Release planning for 2.063

[Johannes Pfau]

Am Tue, 26 Feb 2013 12:41:27 -0500
schrieb Andrei Alexandrescu <SeeWebsiteForEmail at erdani.org>:

> On 2/26/13 10:34 AM, Dicebot wrote:
> > On Tuesday, 26 February 2013 at 15:29:55 UTC, Steven Schveighoffer
> > wrote:
> >> That is more of a factor of the moratorium on changes while the
> >> release is being tested.
> >>
> >> I think if we branch the new development while a release is in
> >> progress, we shouldn't have this problem.
> >>
> >> -Steve
> >
> > According to approved release process in wiki we already are
> > supposed to do it. (Only other way around, branching new release
> > without freezing master).
> 
> It has happened for the past 2-3 cycles already.
> 
> Andrei

That's not the same thing though.

The important part is the time span _between_ feature freeze and
release. This is the time where the release is being prepared,
regressions get fixed and no new features are accepted. More time
between feature freeze and release should therefore lead to better
tested releases and less stress for developers.

According to the wiki process that time span would have been date of
new release - date of old release = 7 weeks.

The last pull request pushed to master included in the beta was
https://github.com/D-Programming-Language/dmd/pull/1342

that was only 11 days before the actual release date so our feature
freeze period was only 11 days.