From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XiIhS-0000Jp-AJ for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 07:57:18 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.213.178 as permitted sender) client-ip=209.85.213.178; envelope-from=laanwj@gmail.com; helo=mail-ig0-f178.google.com; Received: from mail-ig0-f178.google.com ([209.85.213.178]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1XiIhR-0008Nq-Gc for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 07:57:18 +0000 Received: by mail-ig0-f178.google.com with SMTP id h3so3441853igd.17 for ; Sun, 26 Oct 2014 00:57:12 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.107.165.76 with SMTP id o73mr14945821ioe.1.1414310232109; Sun, 26 Oct 2014 00:57:12 -0700 (PDT) Received: by 10.64.249.170 with HTTP; Sun, 26 Oct 2014 00:57:12 -0700 (PDT) Date: Sun, 26 Oct 2014 08:57:12 +0100 Message-ID: From: Wladimir To: Bitcoin Dev 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: 1XiIhR-0008Nq-Gc Subject: [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: Sun, 26 Oct 2014 07:57:18 -0000 Now that headers-first is merged it would be good to do a 0.10 release soon. Not *too* soon as a major code change like that takes some time to pan out, but I'd like to propose the following: - November 18: split off 0.10 branch, translation message and feature freeze - December 1: release 10.0rc1, start Release Candidate cycle That leaves three weeks until the freeze. After the release and branch split-off, the RC cycle will run until no critical problems are found. For major releases this is usually more painful than for stable releases, but if we can keep to these dates I'd expect the final release no later than January 2015. Let's aim to have any pending development for 0.10 merged before November 18. Major work that I'm aware of is: - BIP62 (#5134, #5065) - Verification library (#5086, #5118, #5119) - Gitian descriptors overhaul, so that Gitian depends = Travis depends (#4727) - Autoprune (#4701) - Add "warmup mode" for RPC server (#5007) - Add unauthenticated HTTP REST interface (#2844) Let me know if there is anything else you think is ready (and not too risky) to be in 0.10. You can help along the development process by participating in testing and reviewing of the mentioned pull requests, or just by testing master and reporting bugs and regressions. Note: I intended the 0.10 release to be much sooner. The reason that this didn't pan out is that I insisted on including headers-first, and this took longer than expected. There seems to be a preference to switch to a fixed (instead of feature-based) 6-month major release schedule, ie - July 2015: 0.11.0 (or whatever N+1 release is called) - January 2016: 0.12.0 (or whatever N+2 release is called) - July 2016: 0.13.0 (or whatever N+3 release is called) Wladimir