1.9 code freeze! (was: mercurial at 14687: new changeset (stable))

[Thomas Arendsen Hein]

* Mercurial Commits <hg at intevation.org> [20110619 00:05]:
> New changeset (stable) in mercurial:
> 
> http://selenic.com/repo/hg//rev/15200b46165b
> changeset:   14687:15200b46165b
> branch:      stable
> tag:         tip
> parent:      14508:07722bb8a08c
> parent:      14686:6ab8b17adc03
> user:        Matt Mackall <mpm at selenic.com>
> date:        Sat Jun 18 17:03:01 2011 -0500
> summary:     merge default branch into stable to mark the start of the code freeze

Yay, 1.9 is near!

http://mercurial.selenic.com/wiki/TimeBasedReleasePlan#Major_releases
contains:
 * -2 weeks: feature freeze
 * -2 weeks: bug-stomping sprint
 * -1 week: code freeze
 * -1 week: prerelease testing window with binaries available
 * -1 week: stable tracks tip until release
 * 0: major release

But what actually seems to happen is:
 * -2 weeks: code freeze
 * -2 weeks: default merged into stable,
             stable merged into default once or twice a day.
 * -2 weeks: bug-stomping sprint
 * -1 week: prerelease testing window with binaries available
 * 0: major release

This means:
1. the wiki page is wrong
2. when the code freeze and merge happens and the bug-stomping did
   not yet solve enough bugs, the stable branch becomes more
   unstable than this wiki page suggests

I suggest that the wiki page will be adjusted, as I hope that nobody
blindly pulls and installs from the stable branch in a production
environment and thus should notice the number of new changes.

OK?

Regards,
Thomas

-- 
thomas at intevation.de - http://intevation.de/~thomas/ - OpenPGP key: 0x5816791A
Intevation GmbH, Neuer Graben 17, 49074 Osnabrueck - AG Osnabrueck, HR B 18998
Geschaeftsfuehrer: Frank Koormann, Bernhard Reiter, Dr. Jan-Oliver Wagner