From: Wladimir <laanwj@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Bitcoin core 0.11 planning
Date: Mon, 11 May 2015 15:00:03 +0000 [thread overview]
Message-ID: <CA+s+GJDtduxkc4aVL_s_vhu_jh+3XmnuP2N6UHD=FcLiiZAUmQ@mail.gmail.com> (raw)
In-Reply-To: <20150428074414.GA19918@amethyst.visucore.com>
A reminder - feature freeze and string freeze is coming up this Friday the 15th.
Let me know if your pull request is ready to be merged before then,
Wladimir
On Tue, Apr 28, 2015 at 7:44 AM, Wladimir J. van der Laan
<laanwj@gmail•com> wrote:
> Hello all,
>
> The release window for 0.11 is nearing, I'd propose the following schedule:
>
> 2015-05-01 Soft translation string freeze
> Open Transifex translations for 0.11
> Finalize and close translation for 0.9
>
> 2015-05-15 Feature freeze, string freeze
>
> 2015-06-01 Split off 0.11 branch
> Tag and release 0.11.0rc1
> Start merging for 0.12 on master branch
>
> 2015-07-01 Release 0.11.0 final (aim)
>
> In contrast to former releases, which were protracted for months, let's try to be more strict about the dates. Of course it is always possible for last-minute critical issues to interfere with the planning. The release will not be held up for features, though, and anything that will not make it to 0.11 will be postponed to next release scheduled for end of the year.
>
> Wladimir
prev parent reply other threads:[~2015-05-11 15:00 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-28 7:44 Wladimir J. van der Laan
2015-04-28 10:49 ` Peter Todd
2015-04-28 11:01 ` Pieter Wuille
2015-04-28 13:42 ` Peter Todd
[not found] ` <CA+s+GJBeZkWSKn4igC1ksynoQLfUpUtHBesq9MPi6yRqZZr4Gw@mail.gmail.com>
2015-05-11 14:49 ` [Bitcoin-development] Fwd: " Wladimir
2015-05-11 15:00 ` Wladimir [this message]
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='CA+s+GJDtduxkc4aVL_s_vhu_jh+3XmnuP2N6UHD=FcLiiZAUmQ@mail.gmail.com' \
--to=laanwj@gmail$(echo .)com \
--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