BexarReleaseScheduleSpec
Revision as of 23:17, 9 November 2010 by ThierryCarrez (talk)
- Launchpad Entry: bexar-release-schedule
- Created: 2011-11-03
- Contributors: ThierryCarrez
Summary
tbd
Release Note
tbd
Rationale
tbd
User stories
tbd
Assumptions
We want at least two more three-month cycles.
Design
Proposed Solution
This solution aims at releasing before Ubuntu FeatureFreeze (for Bexar) and at Ubuntu FinalFreeze (for C).
Pre-cycle Prep:
Oct 28 | Nov 4 |
Cycle for Bexar:
Nov 18 | Nov 25 | Dec 2 | Dec 9 | Dec 16 | Dec 23 | Dec 30 | Jan 6 | Jan 13 | Jan 20 | Jan 27 |
BF | FF | GF | ||||||||
Development (9 weeks) | QA |
Cycle for C:
Feb 10 | Feb 17 | Feb 24 | Mar 3 | Mar 10 | Mar 17 | Mar 24 | Mar 31 | Apr 7 |
BF | FF | GF | ||||||
Development (7 weeks) | QA |
This places the next design summit either the week of April 25 or the week of May 2nd.
Key
- ODS: Openstack Design Summit, Tuesday to Friday.
- BF: Branch merge proposal Freeze, Thursday. All branches should be proposed by BF.
- FF: Feature Freeze, Thursday. All branches should be merged by FF.
- GF: Gamma Freeze, Tuesday. Gamma release is used to test the release for critical issues.
- RC: Release Candidate on Tuesday. Release on Thursday. Acts of god are required to change the RC.
Ubuntu dates
- Feb 24: Natty Narwhal feature freeze
- Apr 14: Natty Narwhal final freeze
- Apr 28: Ubuntu 11.04 release
- May 9: UDS-O (Budapest)
Implementation
tbd
Test/Demo Plan
n/a
Unresolved issues
tbd
BoF agenda and discussion
tbd