From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1RSeu2-0001VB-9Z for bitcoin-development@lists.sourceforge.net; Tue, 22 Nov 2011 01:12:02 +0000 X-ACL-Warn: Received: from zinan.dashjr.org ([173.242.112.54]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1RSeu1-0002iV-Il for bitcoin-development@lists.sourceforge.net; Tue, 22 Nov 2011 01:12:02 +0000 Received: from ishibashi.localnet (fl-184-4-160-40.dhcp.embarqhsd.net [184.4.160.40]) (Authenticated sender: luke-jr) by zinan.dashjr.org (Postfix) with ESMTPSA id EC694560010 for ; Tue, 22 Nov 2011 01:11:54 +0000 (UTC) From: "Luke-Jr" To: bitcoin-development@lists.sourceforge.net Date: Mon, 21 Nov 2011 20:11:46 -0500 User-Agent: KMail/1.13.7 (Linux/3.1.0-gentoo; KDE/4.6.5; x86_64; ; ) References: In-Reply-To: X-PGP-Key-Fingerprint: CE5A D56A 36CC 69FA E7D2 3558 665F C11D D53E 9583 X-PGP-Key-ID: 665FC11DD53E9583 X-PGP-Keyserver: x-hkp://subkeys.pgp.net MIME-Version: 1.0 Content-Type: Text/Plain; charset="windows-1252" Content-Transfer-Encoding: 7bit Message-Id: <201111212011.47683.luke@dashjr.org> X-Spam-Score: -1.2 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.2 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain X-Headers-End: 1RSeu1-0002iV-Il Subject: Re: [Bitcoin-development] State of Bitcoin Development: November Brain Dump X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 22 Nov 2011 01:12:02 -0000 On Monday, November 21, 2011 8:06:27 PM Gavin Andresen wrote: > Finding the money to hire some professional QA people to help create > test plans and then execute them (the test plans, not the QA people) > is one possible answer. Not prioritizing some unannounced "release schedule" over getting bugs fixed before making the release is another part of the answer, at least.