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-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1TJSmZ-00044n-Ks for bitcoin-development@lists.sourceforge.net; Wed, 03 Oct 2012 17:30:51 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.175 as permitted sender) client-ip=209.85.212.175; envelope-from=gavinandresen@gmail.com; helo=mail-wi0-f175.google.com; Received: from mail-wi0-f175.google.com ([209.85.212.175]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1TJSmY-0008Tw-VU for bitcoin-development@lists.sourceforge.net; Wed, 03 Oct 2012 17:30:51 +0000 Received: by mail-wi0-f175.google.com with SMTP id hq4so2099348wib.10 for ; Wed, 03 Oct 2012 10:30:44 -0700 (PDT) MIME-Version: 1.0 Received: by 10.180.79.34 with SMTP id g2mr6387515wix.19.1349285444707; Wed, 03 Oct 2012 10:30:44 -0700 (PDT) Received: by 10.194.17.138 with HTTP; Wed, 3 Oct 2012 10:30:44 -0700 (PDT) In-Reply-To: References: <506C6488.8080007@mistfpga.net> Date: Wed, 3 Oct 2012 13:30:44 -0400 Message-ID: From: Gavin Andresen To: Bitcoin Development List Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1TJSmY-0008Tw-VU Subject: Re: [Bitcoin-development] Fwd: Re: Bitcoin Testing Project 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: Wed, 03 Oct 2012 17:30:51 -0000 I had hope the Testing Project would be self-organizing, with somebody taking on the QA lead role and figuring out the hard questions like: + How to do fundraising? + If/when bitcoins are available, how to decide who gets rewarded for what? + If somebody wants to help, how do they start? Steve jumped in and started creating a gazillion tests cases, which is great, but creating test cases isn't the hard part. Creating a "community" of testing that gets things done is the hard part that I, frankly, don't have time to do. I hoped that the BetterMeans platform would help, but it sounds like it was more of a hindrance than a help. Ok: live and learn. Failed experiment, lets move on... So, RE: moving on: I'd like to tag a 0.7.1rc1 release in the next few days (I'll start another thread about that). How about a very short-term goal of getting these QA deliverables: 1. A process for QA testers to sanity-test release builds, and sign-off as "Tested/problems found" or "Tested/OK" 2. Some place online I can look to see if all of our supported platforms have been tested before promoting a release candidate to "final release" PS: Thanks to Peter for responding to the "what's the relationship between the Foundation and the Testing Project" (executive summary: no relationship right now). -- -- Gavin Andresen