|
Size: 1591
Comment:
|
Size: 1610
Comment: cat and style fixes
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Time-Based Release Plan == | = Time-based release plan = |
| Line 4: | Line 4: |
| === Major Releases: === | == Major releases == |
| Line 25: | Line 25: |
| === Minor Releases: === | == Minor releases == |
| Line 31: | Line 31: |
---- CategoryDeveloper |
Time-based release plan
Up until version 1.1, Mercurial took 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.
1. Major releases
Mercurial now follows a 4-month cycle with the following release dates:
- Mar 1st
- 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
- -1 week: stable tracks tip until release
- 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.
2. Minor releases
Minor releases will be made by tagging the current state of the stable branch, which is continually kept in a production-ready state.
Releases will be made in a timely manner for significant behavior regressions, data integrity issues, or security issues.
Barring such issues, minor releases will be made on or about the first of every month that doesn't coincide with a major release.