Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V9lRj-00025S-R6 for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 00:29:47 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.170 as permitted sender) client-ip=209.85.212.170; envelope-from=gavinandresen@gmail.com; helo=mail-wi0-f170.google.com; Received: from mail-wi0-f170.google.com ([209.85.212.170]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V9lRi-0008Dr-SK for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 00:29:47 +0000 Received: by mail-wi0-f170.google.com with SMTP id hi8so29956wib.5 for ; Wed, 14 Aug 2013 17:29:40 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.183.43 with SMTP id ej11mr203506wic.9.1376526580592; Wed, 14 Aug 2013 17:29:40 -0700 (PDT) Received: by 10.194.156.163 with HTTP; Wed, 14 Aug 2013 17:29:40 -0700 (PDT) Date: Thu, 15 Aug 2013 10:29:40 +1000 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c3543edc357f04e3f19152 X-Spam-Score: -0.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 1.0 HTML_MESSAGE BODY: HTML included in message -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: 1V9lRi-0008Dr-SK Subject: [Bitcoin-development] Version 0.9 goals 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: Thu, 15 Aug 2013 00:29:48 -0000 --001a11c3543edc357f04e3f19152 Content-Type: text/plain; charset=ISO-8859-1 It feels to me like we're close to a 0.9 "feature freeze" / start of release cycle; I'd like to talk a little bit about what we'd like to see in the final 0.9 release. My list: Bug: I'd really like to see the leveldb corruption issue (mostly on OSX, it seems) fixed. This is hard because it can't be reliably reproduced, and, at least on my machine, takes weeks to occur. Help needed to reproduce/fix, see https://github.com/bitcoin/bitcoin/issues/2770 for what we know about the problem. Payment Protocol support is ready to be pulled ( https://github.com/bitcoin/bitcoin/pull/2539) . Unless there are major objections, I will pull it tomorrow (it has already gone through two rounds of bounty-driven QA testing, so I'm convinced it is ready). I'd love for 0.9 to contain sipa's "headers first" initial block download optimization; I think it is a big enough improvement to justify making the 0.9 test/release cycle longer. Coin control (https://github.com/bitcoin/bitcoin/pull/2343). The autotools work (https://github.com/bitcoin/bitcoin/pull/2805). Gitian-build with the latest openssl and Qt5. Perhaps update the version of Debian VMs that we gitian-build with. I plan on spending about half my time on code review and helping get pull requests tested, and the other half of my time working on code that probably won't make it into the 0.9 release. -- -- Gavin Andresen --001a11c3543edc357f04e3f19152 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
It feels to me like we're close to a 0.9 "feature= freeze" / start of release cycle; I'd like to talk a little bit a= bout what we'd like to see in the final 0.9 release.

My list:

Bug: =A0I'd really like to see the le= veldb corruption issue (mostly on OSX, it seems) fixed. This is hard becaus= e it can't be reliably reproduced, and, at least on my machine, takes w= eeks to occur. Help needed to reproduce/fix, see=A0https://github.com/bitcoin/bitcoin/issue= s/2770 for what we know about the problem.

Payment Protocol support is ready to be pulled (https://github.com/bitcoi= n/bitcoin/pull/2539) . Unless there are major objections, I will pull i= t tomorrow (it has already gone through two rounds of bounty-driven QA test= ing, so I'm convinced it is ready).

I'd love for 0.9 to contain sipa's "header= s first" initial block download optimization; I think it is a big enou= gh improvement to justify making the 0.9 test/release cycle longer.



Gitian-build with the latest openssl and Qt5. Perhaps u= pdate the version of Debian VMs that we gitian-build with.

I plan on spending about half my time on code review and helping g= et pull requests tested, and the other half of my time working on code that= probably won't make it into the 0.9 release.

--
--
Gavin Andresen
--001a11c3543edc357f04e3f19152--