Release Schedule
The main stages of the Linaro May 2011 release are as follows:
Stage |
Expected |
Explanation |
More Information |
Call for Requirements |
2010-07-22 |
11.05 Cycle begins with Call for Requirements to Members |
|
Beta Technical Requirements |
2010-09-15 |
11.05 Technical Requirements analyzed at TSC |
|
Sign off Tech Requirements |
2010-10-13 |
TSC sign-off of Technical Requirements, blueprints for 11.05 in place |
add link here |
Linaro@UDS |
2010-10-25 |
Engineers meet to discuss Blueprints and requirements |
|
Blueprint Open Sessions |
2010-11-18 |
11.05 Blueprints agreed against Technical Requirements |
add link here |
Feature Definition Freeze |
2010-11-25 |
All prospective features will be defined and acknowledged by the release team. |
|
Board Identification Deadline |
2010-11-25 |
Boards identified for release nominated by members & agreed with VP Engineering |
|
Alpha 1 Release |
2010-12-02 |
First alpha of 11.05 Linaro release |
|
Import Freeze |
2010-12-30 |
All packages from Ubuntu and the Working groups will be imported. |
|
BSP Code Deadline |
2010-12-30 |
BSPs and support code available to Landing Teams. |
|
Linaro Platform Sprint |
2011-01-10 |
Engineers meet to work intensively on Blueprints |
|
TSC Face-to-Face Meeting |
2011-01-12 |
TSC review 11.5 against Technical Specification |
|
Alpha 2 Release |
2011-02-03 |
Second alpha of the 11.05 Linaro release. |
|
Feature Freeze |
2011-02-24 |
All proposed features will either be at a beta or postponed stage. |
|
Board Support Review |
2011-02-24 |
All proposed Boards for LEB release are reviewed to ensure they are on track |
|
Alpha 3 Release |
2011-03-03 |
Third alpha of the 11.05 Linaro release. |
|
Board Support Review 2 |
2011-03-24 |
Second LEB board review to ensure support is on track |
|
Beta Freeze |
2011-03-24 |
From now on all uploads to the main Linaro archive will have to be approved by the release team. |
|
Beta Release |
2011-03-31 |
Beta of the 11.05 Linaro release. |
|
Final Freeze |
2011-04-14 |
From now on all changes to the archive must be approved by the release team. Only critical bugs will be fixed. |
|
Beta 2 Release |
2011-04-28 |
Second Beta of the 11.05 Linaro release. |
|
Release Candidate |
2011-05-21 |
Complete, stable and ready to test by any user. Ideally very little changes happen between this and the final release. |
|
Final Release |
2011-05-28 |
Final version of the Linaro 11.05 release. |
Legend
|
Face-to-face events |
|
Releases |
Freeze dates and uploads
Date |
Explanation |
2011/04/14 |
The Ubuntu main archive and seeded packages are frozen. Only important bug fixes will be allowed to packages that are included in the Ubuntu images. Packages that are in main, universe, multiverse, and overlays that are not part of an Ubuntu image can continue to be uploaded. |
2011/04/21 |
Only Ubuntu release blocking bugs will be fixed from this period onwards. Changes to non-seeded packages can continue to be made as before. |
2011/04/26 |
Changes to unseeded universe and multiverse packages are frozen. Changes to overlays can continue. |
2011/04/28 |
Ubuntu final release (Natty). |
2011/04/29 |
Changes to Natty archive packages can be made using the natty-updates archive. Fixes first go into natty-proposed and when tested and verified are uploaded to natty-updates to be included in Linaro images. Both natty-proposed and natty-updates are enabled on theLinaro images for testing. |
2011/05/19 |
Linaro Release Candidate images are selected. All updates to packages need to be tested and in the natty-updates archive by this date. natty-proposed is disabled from the images. |
2011/05/21 |
Linaro Release Candidate made. Only critical bug fixes will be made from this period onwards using either the natty-updates mechanism or overlays if no over solution is available. |
2011/05/28 |
Linaro 11.05 final images released |
Adding New Features
From feature freeze onwards, no new features will be added to the release. At that time it is expected that any new features are substantially complete and ready for testing. Feature freeze allows widespread user testing, feedback and bug reports to be generated and gives developers the time to respond before the final release. By feature freeze, software should have all new features developed, be testable and integrated into the release.
Cycles/1105/Schedule (last modified 2011-04-26 09:28:43)