[Bitcoin-development] Bitcoin Core 0.10 release schedule

2014-10-26 Thread Wladimir
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


Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule

2014-10-26 Thread odinn
-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-

--
___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development


Re: [Bitcoin-development] Bitcoin Core 0.10 release schedule

2014-10-26 Thread odinn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512

Thanks,

Followup question on https://github.com/bitcoin/bitcoin/pull/3959 :

This describes current dust change handling:

(gavinandresen)
https://github.com/bitcoin/bitcoin/pull/3959/files#r13494256

Related Question:  This describes how wallets would let you know a
transaction is 'precious' with a flag --
(jgarzik)
https://github.com/bitcoin/bitcoin/pull/3753#issuecomment-49464772

- -- however, it doesn't appear to be part of 0.10 anymore ~ what is it
that would keep it from being incorporated into 0.10?
(or was that addressed by a later commit?)

Possibly also related (suggested dusting feature):
https://github.com/bitcoin/bitcoin/issues/4079#issuecomment-41010593

Thanks in advance for your responses.


Wladimir wrote:
 On Sun, Oct 26, 2014 at 9:55 AM, odinn
 odinn.cyberguerri...@riseup.net wrote:
 -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
 
 Yes, floating/smart fees has been merged a while ago
 
 - https://github.com/bitcoin/bitcoin/pull/3959 -
 https://github.com/bitcoin/bitcoin/pull/4250
 
 Wladimir
 

- -- 
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-

iQEcBAEBCgAGBQJUTTq8AAoJEGxwq/inSG8C8PYH/jrZIgecpEiwUYdRGT/dxvrE
qHrlsJz8aPY/E/ojNE4MY4Con5seH2IRL+qg14pZvIQNJSipRYejh0BeqQ2YkfAF
leEt8PlpblNqV0Ieq1VmdJK5wnF3crNZsNdPv73Z7UXplXo8sG+lYGENgC11s+wN
QI29F3Kkrqk66aa6VmRbNzRIgL1JYfTkZLba9ApZNxJsugeOgmlOQw6+q5hgChKy
lxN5s+P/wohH0n047ksYdiMnXbZwPL2scUEN87D74KYqYdCa6AB7vMkLETO2msSg
ndC9ge8LfTODlEuFA9rQ8CgLAkwVWCaCbqph7iqTt6Cvdnqeo9XvlrpcB2B31hI=
=xn6P
-END PGP SIGNATURE-

--
___
Bitcoin-development mailing list
Bitcoin-development@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bitcoin-development