|
Size: 821
Comment:
|
Size: 1720
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| == Time-Base Release Plan == | #pragma section-numbers 2 = Time-based Release Plan = |
| Line 3: | Line 4: |
| 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. | How we manage releases. |
| Line 5: | Line 6: |
| Post-1.1, I propose a 4-month cycle with the following release dates: | <<TableOfContents>> |
| Line 7: | Line 8: |
| * Mar 1st - [http://www.selenic.com/pipermail/mercurial-devel/2009-January/010031.html Feature freeze Feb 14th] | == Theory == Up until version 1.1, Mercurial took a "when it's ready" approach to releases. Starting with version 1.2, we've switch to a consistent calendar-based release schedule. This helps us get bug fixes and new features into our user's hands more quickly, improve our planning process, and keep our development cycles from growing stagnant. == Major releases == Mercurial now follows a 4-month cycle with the following release dates: * Mar 1st |
| Line 17: | Line 26: |
| * -1 week: stable tracks tip until release | |
| Line 19: | Line 29: |
'''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 (e.g. 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. == 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. ---- CategoryDeveloper CategoryProcess |
Time-based Release Plan
How we manage releases.
Contents
1. Theory
Up until version 1.1, Mercurial took a "when it's ready" approach to releases. Starting with version 1.2, we've switch to a consistent calendar-based release schedule. This helps us get bug fixes and new features into our user's hands more quickly, improve our planning process, and keep our development cycles from growing stagnant.
2. 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 (e.g. 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.
3. 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.