Software update content is managed by bugzilla. Only the fixes for bugs with flag MeeGo_Update_Release_Blocker = Approved can be accepted into an update. If you want to include one bug fix into an update, you should first propose it with MeeGo_Update_Release_Blocker = Proposed. Then CCB will review and decide whether it’s a real update release blocker or not by setting MeeGo_Update_Release_Blocker to Approved or Rejected. Generally, the approved update release bugs must first be fixed and verified in MeeGo Trunk. For detailed criteria, please see http://wiki.meego.com/Quality/Bug_Life_Cycle_and_Handling#MeeGo_update_bug_fix_acceptance_criteria.
With some packages accepted, the release engineer will create a testing repo for internal release. The release is of form of repo with all updated packages. Such a repo is very unique in that
The testing repo should be smoke-tested by responsible release engineer before it is released for QA and other users’ testing. The testing repo will be uploaded to http://repo.meego.com/MeeGo/builds/1.1/. The release engineer will post announcement of the repo updates on “meego-releases” mailing list. If the end users run into any issues about the update, please file a bug on bugzilla. QA will do testing and give quality report for the build.
For each milestone, after all testing repo has been tested, the release engineer will push all changes in *:Update:Testing projects to *:Update projects, and create the final release repo from *:Update projects.
|1||2010.11.26||http://repo.meego.com/MeeGo/updates/1.1/||http://meego.com/downloads/releases/updates/meego-v1.1.1-core-update http://meego.com/downloads/releases/updates/meego-v1.1.1-netbook-update http://meego.com/downloads/releases/updates/meego-v1.1.1-ivi-update|
|To be updated|