From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1V9v7L-0000Qt-OV for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 10:49:23 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.214.53 as permitted sender) client-ip=209.85.214.53; envelope-from=laanwj@gmail.com; helo=mail-bk0-f53.google.com; Received: from mail-bk0-f53.google.com ([209.85.214.53]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1V9v7H-0007DL-LD for bitcoin-development@lists.sourceforge.net; Thu, 15 Aug 2013 10:49:23 +0000 Received: by mail-bk0-f53.google.com with SMTP id d7so168152bkh.26 for ; Thu, 15 Aug 2013 03:49:13 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.205.24.131 with SMTP id re3mr10323412bkb.8.1376563753226; Thu, 15 Aug 2013 03:49:13 -0700 (PDT) Received: by 10.204.111.131 with HTTP; Thu, 15 Aug 2013 03:49:13 -0700 (PDT) In-Reply-To: References: Date: Thu, 15 Aug 2013 12:49:13 +0200 Message-ID: From: Wladimir To: Gavin Andresen Content-Type: multipart/alternative; boundary=20cf301e2dd185c0f704e3fa39f0 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 (laanwj[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: 1V9v7H-0007DL-LD Cc: Bitcoin Dev Subject: Re: [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 10:49:23 -0000 --20cf301e2dd185c0f704e3fa39f0 Content-Type: text/plain; charset=UTF-8 On Thu, Aug 15, 2013 at 2:29 AM, Gavin Andresen wrote: > 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. > > 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). > No objections from me, I've already looked at the code a few times and did some testing here and there, looks good for merging. > 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. > Yep, that'd be great. > 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. > Fully agreed about payment protocol, autotools and Qt5 build. I'm still not very excited about coin control (and last time I looked at the code, it has an issue that it introduced statefulness into the wallet model - a bane for concurrency. But that may be resolved?) . Anyway, many people seem to want that so it's fine with me, given that the issues are fixed. Wladimir --20cf301e2dd185c0f704e3fa39f0 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable

On Thu, Aug 15, 2013 at 2:29 AM, Gavin Andr= esen <gavinandresen@gmail.com> wrote:
= It feels to me like we're close to a 0.9 "feature freeze" / s= tart of release cycle; I'd like to talk a little bit about what we'= d like to see in the final 0.9 release.

Payment Protocol support is ready to be pulled (https:/= /github.com/bitcoin/bitcoin/pull/2539) . Unless there are major objecti= ons, I will pull it tomorrow (it has already gone through two rounds of bou= nty-driven QA testing, so I'm convinced it is ready).

No objections from me, I'v= e already looked at the code a few times and did some testing here and ther= e, looks good for merging.
=C2=A0
I'd love for 0.9 to contain sipa's "headers first" i= nitial block download optimization; I think it is a big enough improvement = to justify making the 0.9 test/release cycle longer.

Yep, that'd be great.
=C2=A0
Coin control (https://github.com/bitcoin/bitcoin/pull/2343).


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

Fully agreed about payment protocol, autotools = and Qt5 build.=C2=A0

I'm still not very excited about coin control (and = last time I looked at the code, it has an issue that it introduced stateful= ness into the wallet model - a bane for concurrency. But that may be resolv= ed?) . Anyway, many people seem to want that so it's fine with me, give= n that the issues are fixed.

Wladimir
--20cf301e2dd185c0f704e3fa39f0--