diff options
author | Luke Dashjr <luke@dashjr.org> | 2014-10-26 08:53:37 +0000 |
---|---|---|
committer | bitcoindev <bitcoindev@gnusha.org> | 2014-10-26 08:53:46 +0000 |
commit | 05fbbc97c503ceef4452d141fcbc26634df6973b (patch) | |
tree | c2b8fef98b448485be53eff2f1e131b937fbfa02 | |
parent | b1dea1399e07bec2031c23d978239e8c2596c706 (diff) | |
download | pi-bitcoindev-05fbbc97c503ceef4452d141fcbc26634df6973b.tar.gz pi-bitcoindev-05fbbc97c503ceef4452d141fcbc26634df6973b.zip |
Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
-rw-r--r-- | 6b/0097080548e3f88e67fddcaa57f94f2469c296 | 80 |
1 files changed, 80 insertions, 0 deletions
diff --git a/6b/0097080548e3f88e67fddcaa57f94f2469c296 b/6b/0097080548e3f88e67fddcaa57f94f2469c296 new file mode 100644 index 000000000..bcd63181e --- /dev/null +++ b/6b/0097080548e3f88e67fddcaa57f94f2469c296 @@ -0,0 +1,80 @@ +Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] + helo=mx.sourceforge.net) + by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) + (envelope-from <luke@dashjr.org>) id 1XiJa6-0006YR-P0 + for bitcoin-development@lists.sourceforge.net; + Sun, 26 Oct 2014 08:53:46 +0000 +Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of dashjr.org + designates 192.3.11.21 as permitted sender) + client-ip=192.3.11.21; envelope-from=luke@dashjr.org; + helo=zinan.dashjr.org; +Received: from zinan.dashjr.org ([192.3.11.21]) + by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) + id 1XiJa5-0001ez-Nc for bitcoin-development@lists.sourceforge.net; + Sun, 26 Oct 2014 08:53:46 +0000 +Received: from ishibashi.localnet (unknown + [IPv6:2001:470:5:265:61b6:56a6:b03d:28d6]) + (Authenticated sender: luke-jr) + by zinan.dashjr.org (Postfix) with ESMTPSA id 35F72108039F; + Sun, 26 Oct 2014 08:53:40 +0000 (UTC) +From: Luke Dashjr <luke@dashjr.org> +To: Wladimir <laanwj@gmail.com> +Date: Sun, 26 Oct 2014 08:53:37 +0000 +User-Agent: KMail/1.13.7 (Linux/3.17.1-gentoo-r1; KDE/4.12.5; x86_64; ; ) +References: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com> +In-Reply-To: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com> +X-PGP-Key-Fingerprint: E463 A93F 5F31 17EE DE6C 7316 BD02 9424 21F4 889F +X-PGP-Key-ID: BD02942421F4889F +X-PGP-Keyserver: hkp://pgp.mit.edu +MIME-Version: 1.0 +Content-Type: Text/Plain; + charset="iso-8859-1" +Content-Transfer-Encoding: 7bit +Message-Id: <201410260853.38850.luke@dashjr.org> +X-Spam-Score: -2.1 (--) +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 SPF_PASS SPF: sender matches SPF record + -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay + domain +X-Headers-End: 1XiJa5-0001ez-Nc +Cc: bitcoin-development@lists.sourceforge.net +Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule +X-BeenThere: bitcoin-development@lists.sourceforge.net +X-Mailman-Version: 2.1.9 +Precedence: list +List-Id: <bitcoin-development.lists.sourceforge.net> +List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe> +List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development> +List-Post: <mailto:bitcoin-development@lists.sourceforge.net> +List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help> +List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>, + <mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe> +X-List-Received-Date: Sun, 26 Oct 2014 08:53:47 -0000 + +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 + + |