Time-Base Release Plan
Mercurial has so far taken a "when it's ready" approach to releases. As we mature, it probably makes sense to switch to a consistent release schedule. This will help us get bug fixes and new features into our user's hands more quickly, improve our planning process, and hopefully keep our development cycles from growing stagnant.
Post-1.1, I propose a 4-month cycle with the following release dates:
Mar 1st - [http://www.selenic.com/pipermail/mercurial-devel/2009-January/010031.html Feature freeze Feb 14th]
- July 1st
- Nov 1st
In each cycle, we have:
- -2 weeks: feature freeze
- -2 weeks: bug-stomping sprint
- -1 week: code freeze
- -1 week: prerelease testing window with binaries available
- 0: major release
- 1 month: Zero or more bugfix releases