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 ) id 1XiemC-0004dw-6t for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 07:31:40 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.223.177 as permitted sender) client-ip=209.85.223.177; envelope-from=laanwj@gmail.com; helo=mail-ie0-f177.google.com; Received: from mail-ie0-f177.google.com ([209.85.223.177]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1Xiem9-00057k-RZ for bitcoin-development@lists.sourceforge.net; Mon, 27 Oct 2014 07:31:40 +0000 Received: by mail-ie0-f177.google.com with SMTP id tp5so3760074ieb.22 for ; Mon, 27 Oct 2014 00:31:32 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.162.16 with SMTP id l16mr897681ioe.54.1414395092479; Mon, 27 Oct 2014 00:31:32 -0700 (PDT) Received: by 10.64.249.170 with HTTP; Mon, 27 Oct 2014 00:31:32 -0700 (PDT) In-Reply-To: <201410260853.38850.luke@dashjr.org> References: <201410260853.38850.luke@dashjr.org> Date: Mon, 27 Oct 2014 08:31:32 +0100 Message-ID: From: Wladimir To: Luke Dashjr Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (laanwj[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1Xiem9-00057k-RZ Cc: Bitcoin Dev 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: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Oct 2014 07:31:40 -0000 On Sun, Oct 26, 2014 at 9:53 AM, Luke Dashjr 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