0.10 release process - time based release?

[Michael Ellerman]

On 8/1/06, Robert Collins <robertc at robertcollins.net> wrote:
> I'd like to suggest a change for the release process of bzr - time based
> releases.
>
> Heres the crux of what I suggest:
>
> We release 0.10 Monday September 4th.
> To achieve that, 0.10 rc1 will be released August 28th,
> bzr.dev will be frozen for all bar non-risky bugfixes from August 21st.
>
> This gives us 3 weeks for major feature landings, and 2 weeks to recover
> from any instability.
>
> I'm offering to be the release mgr for this release, as I've done time
> based releases before.

Sounds good to me. The problem I have with the current situation is
that features seem to land faster just before a release, which is
exactly backwards. Your proposal should fix that.

My only worry would be that it will leave larger changes sitting out
in the wild, untested. So I'd propose that in the first 3 weeks,
pretty much anything good gets merged, that way it gets testing and
attention, but if it turns out to be not 100% it comes out before
release.

cheers