On Wed, Sep 30, 2015 at 05:57:42PM +, Luke Dashjr wrote:
> On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
> bitcoin-dev wrote:
> > 2015-12-01
> > ---
> > - Feature freeze
>
> Where is "Consensus freeze"? Shouldn't this be put off until after the HK
>
Any particular reason bitcoin versioning doesn't follow the SemVer spec?
2015-10-01 10:50 GMT+02:00 Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org>:
> On Wed, Sep 30, 2015 at 05:57:42PM +, Luke Dashjr wrote:
> > On Thursday, September 24, 2015 11:25:56 AM
On Thu, Oct 1, 2015 at 10:05 AM, Marcel Jamin via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Any particular reason bitcoin versioning doesn't follow the SemVer spec?
>
We do: a.b.c, the next major version is, 0.12.0, and maintenance releases
are 0.12.1 etc. Release candidates
On Thursday, September 24, 2015 11:25:56 AM Wladimir J. van der Laan via
bitcoin-dev wrote:
> 2015-12-01
> ---
> - Feature freeze
Where is "Consensus freeze"? Shouldn't this be put off until after the HK
workshop in case a hardfork is decided on? Or have we de-coupled it from the
Yes, I believe consensus rule changes don't need to be couple with
major releases, there's no problem that I can see in them being minor
releases if they're not ready on time for a major release.
On Wed, Sep 30, 2015 at 7:57 PM, Luke Dashjr via bitcoin-dev
ACK
On Thu, Sep 24, 2015 at 7:25 AM, Wladimir J. van der Laan via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:
> Hello all,
>
> The next major release of Bitcoin Core, 0.12.0 is planned for the end of
> the year. Let's propose a more detailed schedule:
>
> 2015-11-01
>
Hello all,
The next major release of Bitcoin Core, 0.12.0 is planned for the end of the
year. Let's propose a more detailed schedule:
2015-11-01
---
- Open Transifex translations for 0.12
- Soft translation string freeze (no large or unnecessary changes)
- Finalize and close translation