From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1XiJbn-0002An-9a for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 08:55:31 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of riseup.net designates 198.252.153.129 as permitted sender) client-ip=198.252.153.129; envelope-from=odinn.cyberguerrilla@riseup.net; helo=mx1.riseup.net; Received: from mx1.riseup.net ([198.252.153.129]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.76) id 1XiJbk-0000Vp-QU for bitcoin-development@lists.sourceforge.net; Sun, 26 Oct 2014 08:55:31 +0000 Received: from berryeater.riseup.net (berryeater-pn.riseup.net [10.0.1.120]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (Client CN "*.riseup.net", Issuer "COMODO RSA Domain Validation Secure Server CA" (verified OK)) by mx1.riseup.net (Postfix) with ESMTPS id EDE334190D for ; Sun, 26 Oct 2014 08:55:22 +0000 (UTC) Received: from [127.0.0.1] (localhost [127.0.0.1]) (Authenticated sender: odinn.cyberguerrilla) with ESMTPSA id 47D103F80E Message-ID: <544CB6F2.4000200@riseup.net> Date: Sun, 26 Oct 2014 08:55:14 +0000 From: odinn MIME-Version: 1.0 To: bitcoin-development@lists.sourceforge.net References: In-Reply-To: Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit X-Virus-Scanned: clamav-milter 0.98.4 at mx1 X-Virus-Status: Clean X-Spam-Score: -2.2 (--) 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 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/, no trust [198.252.153.129 listed in list.dnswl.org] -0.0 SPF_HELO_PASS SPF: HELO matches SPF record -0.0 SPF_PASS SPF: sender matches SPF record -0.6 RP_MATCHES_RCVD Envelope sender domain matches handover relay domain -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 0.0 UNPARSEABLE_RELAY Informational: message has unparseable relay lines X-Headers-End: 1XiJbk-0000Vp-QU 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: Sun, 26 Oct 2014 08:55:31 -0000 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Q., re. transaction fee changes / txconfirmtarget described at https://github.com/bitcoin/bitcoin/blob/c8a25189bcb1381eddf46b9a9743ba48e929439e/doc/release-notes.md (for Core 0.10) ~ does this include the floating fees for 0.10 as described at https://bitcoinfoundation.org/2014/07/floating-fees-for-0-10/ ? thanks in advance for clarifications Wladimir wrote: > 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 > > ------------------------------------------------------------------------------ > > _______________________________________________ > Bitcoin-development mailing list > Bitcoin-development@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/bitcoin-development > - -- http://abis.io ~ "a protocol concept to enable decentralization and expansion of a giving economy, and a new social good" https://keybase.io/odinn -----BEGIN PGP SIGNATURE----- iQEcBAEBCgAGBQJUTLbyAAoJEGxwq/inSG8CzkgH/jqh3+RxdFR1sFn8PENbUvKN M3GUF3otRDenuVOY6Gbs1Sv3IBToC1zAR1RdktYeTrfQlCgO89ybASJapqQ6H8XP 7STY99dtZgRxkSwsE5bMHceVlHlSrtCBoPCZpPte9+8KVZUpQ/WNNPhjU84sQTj5 n2wkG7GdtD4vEoLHgLo1yEMoeRcwS8eb7kUeYAdRQbAOdNBqUkcs0FW2yvAnk//M /ubtWoWr7c+Ksozp45I7rtB6UL1YrYMBJURwKsCc62mpnc1rkvedRmQVC1KO/em1 8nAvobRUbrExPtNO8+AkWZsyiSIR+PANV4h3IOHbERC6L8iGrD/QiUjuAjXXwSw= =tplQ -----END PGP SIGNATURE-----