From: odinn <odinn.cyberguerrilla@riseup•net>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule
Date: Sun, 26 Oct 2014 08:55:14 +0000 [thread overview]
Message-ID: <544CB6F2.4000200@riseup.net> (raw)
In-Reply-To: <CA+s+GJA3-qK71TcUCYQ3xOdi+zgE_fB9N6NJkNBUDtWnA-0dcA@mail.gmail.com>
-----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-----
next prev parent reply other threads:[~2014-10-26 8:55 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-26 7:57 Wladimir
2014-10-26 8:53 ` Luke Dashjr
2014-10-27 7:31 ` Wladimir
2014-10-26 8:55 ` odinn [this message]
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=544CB6F2.4000200@riseup.net \
--to=odinn.cyberguerrilla@riseup$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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