From: Luke Dashjr <luke@dashjr•org>
To: Wladimir <laanwj@gmail•com>
Cc: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
Date: Sun, 26 Oct 2014 08:53:37 +0000 [thread overview]
Message-ID: <201410260853.38850.luke@dashjr.org> (raw)
In-Reply-To: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com>
On Sunday, October 26, 2014 7:57:12 AM Wladimir wrote:
> Let me know if there is anything else you think is ready (and not too
> risky) to be in 0.10.
At the very least, we need:
#5106 Bugfix: submitblock: Use a temporary CValidationState to determine ...
#5103 CreateNewBlock and miner_tests: Also check generated template is ...
#5078 Bugfix: CreateNewBlock: Check that active chain has a valid tip ...
(or at least some conclusion for the problem discussed therein)
Harmless/No reason not to have:
#3727 RPC: submitblock: Support for returning specific rejection reasons
#1816 Support for BIP 23 block proposal
#5144 Qt: Elaborate on signverify message dialog warning
#5071 Introduce CNodePolicy for putting isolated node policy code and ...
(futher commits exist that should ideally get in after this is merged)
Debatable (but harmless, and miners seem to want it):
#5077 Enable customising node policy for datacarrier data size with a ...
Luke
next prev parent reply other threads:[~2014-10-26 8:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 7:57 Wladimir
2014-10-26 8:53 ` Luke Dashjr [this message]
2014-10-27 7:31 ` Wladimir
2014-10-26 8:55 ` odinn
2014-10-26 9:10 ` Wladimir
2014-10-26 18:17 ` odinn
2014-10-26 11:44 ` Melvin Carvalho
2014-10-27 7:49 ` Wladimir
2014-10-27 11:24 ` Melvin Carvalho
2014-10-27 11:37 ` Jeff Garzik
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=201410260853.38850.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=laanwj@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