Release Engineering/Release Versioning

Contents 1 Release Versioning 1.1 Official Releases 1.2 Updates for Official Releases 1.3 Developer and Pre-Releases 1.4 Weekly Builds and Build Numbers 1.5 Examples

Release Versioning

In general:

 X.Y – For major releases such as 1.0 and 1.1
 X.Y.80.N - alpha state for release following release X.Y 
 X.Y.90.N - beta state for release following release X.Y
 X.Y.0.N - updates for X.Y release
 X.Y.1.0 – Update Bundles or service packs

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.0.N - updates for X.Y release 
 X.Y.1.0 – Update Bundles or service packs

Developer and Pre-Releases

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

 X.Y.[80|90].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.[80|90].RELEASE_SEQUENCE.DATE.BUILD

Examples

• 0.9.80.N to 0.9.90.N to 1.0.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