Differences between revisions 2 and 3
⇤ ← Revision 2 as of 2009-02-06 15:43:37 →
Size: 821
Editor: MadsKiilerich
Comment:
← Revision 3 as of 2009-02-27 13:35:22 → ⇥
Size: 1180
Editor: mpm
Comment:
Deletions are marked like this. Additions are marked like this.
Line 19: Line 19:

'''Feature freeze:''' bug fixes, template fixes, doc fixes, and translation fixes only. Exceptions may be made for code that can be shown to have no regression or design impact (eg new convert back-ends).

'''Code freeze:''' regression bug fixes, doc fixes and translation fixes only. Exceptions will be made on a case-by-case bases for noteworthy bugs.

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:

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

Feature freeze: bug fixes, template fixes, doc fixes, and translation fixes only. Exceptions may be made for code that can be shown to have no regression or design impact (eg new convert back-ends).

Code freeze: regression bug fixes, doc fixes and translation fixes only. Exceptions will be made on a case-by-case bases for noteworthy bugs.

TimeBasedReleasePlan (last edited 2022-01-06 08:36:10 by RaphaelGomes)