versioning
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision | ||
versioning [2013/01/04 13:16] – [Major, minor, and patch releases] dyrcona | versioning [2018/10/23 11:59] – old revision restored (2017/11/06 22:18) klussier | ||
---|---|---|---|
Line 2: | Line 2: | ||
- | ===== The Versioning Scheme (as of Evergreen 2.0.0) ===== | + | ===== The Versioning Scheme (as of Evergreen 2.1.0) ===== |
The Evergreen project uses a double-decimal format, such as " | The Evergreen project uses a double-decimal format, such as " | ||
Line 8: | Line 8: | ||
==== Major, minor, and patch releases ==== | ==== Major, minor, and patch releases ==== | ||
- | The first number (in our example, the number " | + | The first number (in our example, the number " |
- | The second number (in our example, the number " | + | The second number (in our example, the number " |
The third number (in our example, the number " | The third number (in our example, the number " | ||
- | **NOTE** | ||
- | We don't actually use the above schema any longer. It has been left here for lack of a better explanation of how releases are numbered at the moment. | + | ==== Major/ |
- | ==== Alpha, beta, and release | + | |
- | During the process of finalizing a new major or minor release, the release manager will normally create a series of alpha, beta, and release candidate releases for the purposes of testing, providing feature previews, and supporting documentation and translation efforts. The progression from //alpha// through //release candidate// represents the development team's increasing confidence in the stability and production-readiness of the code, until the //Golden Master// (final release) is published. | + | During the process of finalizing a new major or minor release, the release manager will normally create a series of alpha (optional), beta, and release candidate releases for the purposes of testing, providing feature previews, and supporting documentation and translation efforts. The progression from //alpha// through //release candidate// represents the development team's increasing confidence in the stability and production-readiness of the code, until the //Golden Master// (final release) is published. |
The first alpha release for a given major or minor increment will be labelled //alpha1//, the second alpha release will be labelled //alpha2//, etc. Once the progression from alpha to beta has been made, no further alpha releases will be published. | The first alpha release for a given major or minor increment will be labelled //alpha1//, the second alpha release will be labelled //alpha2//, etc. Once the progression from alpha to beta has been made, no further alpha releases will be published. | ||
- | | + | In addition to actual releases, there are other common deadlines involved in each release process, so we define those here as well. |
- | * **pre-beta**: a brief period (generally a few days) between alpha and beta intended primarily | + | |
- | * the pre-beta period begins with a hard cutoff for merging in feature | + | |
- | * a release is prepared, but no external announcement is made, and no download link is published | + | * **feature slush**: major planning |
- | * developers have two days to check for obvious problems caused by incorrect or missing commits; problems are corrected as needed | + | * at this point, all significant features should either have been merged or at least have LP bugs and pullrequests |
- | * **beta**: | + | * generally scheduled two to three weeks before |
- | * **release candidate**: | + | * **feature |
+ | * no feature branches should be merged beyond this date | ||
+ | * templates updated | ||
+ | * generally one week or less before the beta release | ||
+ | * **beta**: | ||
+ | * all further commits should be for bug fixes, translations, | ||
+ | * database schema is frozen for anything other than bug fixes | ||
+ | * **release candidate**: | ||
* **Golden Master**: no // | * **Golden Master**: no // | ||
===== The Versioning Scheme (prior to Evergreen 2.0.0) ===== | ===== The Versioning Scheme (prior to Evergreen 2.0.0) ===== |
versioning.txt · Last modified: 2022/02/10 13:34 by 127.0.0.1