MeeGo releases will occur every 6 months. Each release cycle will follow the same basic pattern of phases as described below. Each release will contain the MeeGo core and the existing set of MeeGo categories. From this point on, wherever the terms 'Trunk' or 'Release' are used, they should be taken to include both the core and the category-specific Trunks and Releases.
MeeGo releases started with version 1.0. Currently the numbers have no specific meaning, other than that a bigger number means a newer release.
Release content specifications (features) are available in Bugzilla in bugs.meego.com, as well as in Release Trunk and Release branch in build.meego.com. Releases and builds with related release notes, images, etc., are published in repo.meego.com.
|MM0||Concept for release done|
|MM1||All planning done and development started|
|MM2||Intrusive (high risk and priority) changes phase complete|
|MM2.5||Optional checkpoint for features with medium risks|
|MM3||Feature development phase completed|
|MM3.5||Optional checkpoint for bugfixing|
|MM4||Stabilization phase completed|
|MM5||Public MeeGo Release|
|MM5.1, MM5.2,...||Update releases, if needed|
|MM6||End of active Maintenance|
|MM7||End of lifecycle|
The roadmap for MeeGo releases will appear about 18 months (3 release cycles) before the planned release date. Two months before the Trunk opens for new release content, development work starts in the MeeGo working groups to define and freeze the release content specification for the upcoming MeeGo release. Requirements and features are handled in Bugzilla in bugs.meego.com.
The active development phase of a MeeGo release lasts seven months and is split into four parts:
This section describes the maintenance plan, plus the updates and changes, that may be made according to feedback and discussions prior to a 1.1 Release becoming available.
MeeGo aims to get products out to the market from different categories during a one-year period after a release, for the devices to be able to always use the latest and greatest MeeGo software. During this period, a lot of updates may be made to support the release and its users. The goal is to keep the quality stable, so that updates can be put into use without problems. This is a quality-first period.
Fixes are actively integrated for two years after the MeeGo release and security fixes are integrated and updated, when necessary, to existing MeeGo releases.