Release Engineering/Release Versioning

Latest revision as of 17:54, 19 May 2011

Release Versioning

In general:

 X.Y – For major releases such as 1.0 and 1.1
 X.Y.Z – Update Bundles or service packs (X.Y.Z.0)
 X.Y.Z.N - updates for X.Y release
 X.Y.80.N - Intrusive changes and Feature development phases for release following release X.Y 
 X.Y.90.N - Stabilization phase for release following release X.Y
 X.Y.99.N - Release candidate phase for release following release X.Y

Official Releases

MeeGo is released twice a year using a 6-month cycle. The release version has the following scheme:

 X.Y

Updates for Official Releases

Updates for official MeeGo releases can be identified on following versioning scheme:

 X.Y.Z – Update Bundles or service packs for release X.Y (X.Y.Z.0)
 X.Y.Z.N - updates for X.Y.Z release

Developer and Pre-Releases

A Pre-release for next release after X.Y is defined using the following scheme:

 X.Y.[80|90|99].RELEASE_SEQUENCE

Release sequence counter is incremented every time a release is made, usually on a weekly basis in the development cycle but more frequently close to final release.

Weekly Builds and Build Numbers

Weekly builds have the following version scheme:

X.Y.Z.RELEASE_SEQUENCE.DATE.BUILD

Examples

• 0.9.80.N to 0.9.90.N to 1.0.0
• 1.0 is MeeGo 1.0 release
• 1.0.2 is the second update to 1.0
• 1.0.80.N as the pre-release series leading to 1.1
• 1.0.90.N once we hit feature freeze on the product branch
• 1.0.80.1.20100514.1 is a 1.1 pre-release build

Comments

Worth noting that this release numbering system would sort alphanumerically for quite a while if Z and N were allocated 2 digits. Maybe for 1.2 ?