Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.213.52 as permitted sender)
	client-ip=209.85.213.52; envelope-from=laanwj@gmail.com;
	helo=mail-yh0-f52.google.com; 
MIME-Version: 1.0
In-Reply-To: <20150428074414.GA19918@amethyst.visucore.com>
References: <20150428074414.GA19918@amethyst.visucore.com>
Date: Mon, 11 May 2015 15:00:03 +0000
Message-ID: <CA+s+GJDtduxkc4aVL_s_vhu_jh+3XmnuP2N6UHD=FcLiiZAUmQ@mail.gmail.com>
From: Wladimir <laanwj@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] Bitcoin core 0.11 planning
Precedence: list

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 schedul=
e:
>
> 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 t=
ry to be more strict about the dates. Of course it is always possible for l=
ast-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