From: Wladimir <laanwj@gmail.com>
To: Luke Dashjr <luke@dashjr.org>
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
Date: Mon, 27 Oct 2014 08:31:32 +0100 [thread overview]
Message-ID: <CA+s+GJBjXGzH07TTt5E1-sgPQhMrWwqOEXUeFk2Azq4=Tb3V2g@mail.gmail.com> (raw)
In-Reply-To: <201410260853.38850.luke@dashjr.org>
On Sun, Oct 26, 2014 at 9:53 AM, Luke Dashjr <luke@dashjr.org> wrote:
> 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)
OK
> 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)
ACK on the UI change,
I think it would be best to let the full-blown "miner policy class"
wait for 0.11.
> Debatable (but harmless, and miners seem to want it):
> #5077 Enable customising node policy for datacarrier data size with a ...
OK, that's a low-risk change, it just makes what is now a constant configurable.
Wladimir
next prev parent reply other threads:[~2014-10-27 7:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 7:57 [Bitcoin-development] Bitcoin Core 0.10 release schedule Wladimir
2014-10-26 8:53 ` Luke Dashjr
2014-10-27 7:31 ` Wladimir [this message]
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='CA+s+GJBjXGzH07TTt5E1-sgPQhMrWwqOEXUeFk2Azq4=Tb3V2g@mail.gmail.com' \
--to=laanwj@gmail.com \
--cc=bitcoin-development@lists.sourceforge.net \
--cc=luke@dashjr.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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