public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Wladimir <laanwj@gmail•com>
To: Gavin Andresen <gavinandresen@gmail•com>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Version 0.9 goals
Date: Thu, 15 Aug 2013 12:49:13 +0200	[thread overview]
Message-ID: <CA+s+GJDr-KhPdnNEuFAE325OUEa42ukJ_9yXcS8sJ+Y_w9LWyw@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 1498 bytes --]

On Thu, Aug 15, 2013 at 2:29 AM, Gavin Andresen <gavinandresen@gmail•com>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

[-- Attachment #2: Type: text/html, Size: 2624 bytes --]

  parent reply	other threads:[~2013-08-15 10:49 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-08-15  0:29 Gavin Andresen
2013-08-15  8:09 ` Mike Hearn
2013-08-15  8:22   ` slush
2013-08-15  9:02     ` Mike Hearn
2013-08-15 14:32       ` slush
2013-08-15 15:22         ` Mike Hearn
2013-08-15  8:37   ` Pieter Wuille
2013-08-15 21:12   ` Wendell
2013-08-15 10:12 ` Melvin Carvalho
2013-08-15 10:49 ` Wladimir [this message]
2013-08-15 10:56   ` Pieter Wuille

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CA+s+GJDr-KhPdnNEuFAE325OUEa42ukJ_9yXcS8sJ+Y_w9LWyw@mail.gmail.com \
    --to=laanwj@gmail$(echo .)com \
    --cc=bitcoin-development@lists$(echo .)sourceforge.net \
    --cc=gavinandresen@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox