From: Melvin Carvalho <melvincarvalho@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:12:17 +0200 [thread overview]
Message-ID: <CAKaEYhJy9_xij0GcTqUjVQ8gwdvnoRk4DGmGKC0ybDV_acFvug@mail.gmail.com> (raw)
In-Reply-To: <CABsx9T3DM72+8HgNWWZ2HaAgZMQGAPn87L9VVKdkbVkS7sd8Tg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2163 bytes --]
On 15 August 2013 02:29, 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.
>
> 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.
>
+1
Sounds great!
>
> --
> --
> Gavin Andresen
>
>
> ------------------------------------------------------------------------------
> Get 100% visibility into Java/.NET code with AppDynamics Lite!
> It's a free troubleshooting tool designed for production.
> Get down to code-level detail for bottlenecks, with <2% overhead.
> Download for free and get started troubleshooting in minutes.
> http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists•sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>
>
[-- Attachment #2: Type: text/html, Size: 3604 bytes --]
next prev parent reply other threads:[~2013-08-15 10:12 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 [this message]
2013-08-15 10:49 ` Wladimir
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=CAKaEYhJy9_xij0GcTqUjVQ8gwdvnoRk4DGmGKC0ybDV_acFvug@mail.gmail.com \
--to=melvincarvalho@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