BexarReleaseScheduleSpec
Revision as of 12:36, 5 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
Important dates
- Feb 24 (week 8): Natty Narwhal feature freeze
- Apr 14 (week 15): Natty Narwhal final freeze
- Apr 28 (week 17): Ubuntu 11.04 release
- Week 19: UDS-O (Budapest)
- Week 30: OSCON (Portland)
- Aug 18 (week 33): Natty+1 feature freeze
- Sep 22 (week 38): Natty+1 final freeze
- Oct 13 (week 41): Ubuntu 11.10 release
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.
Solution 1: Almost three-month cycle from summit to release
Cycle for Bexar (3+ months):
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 | 4 | 5 |
| ODS | BF | FF | GF | |||||||||||
| Prep | Development (9 weeks) | QA | ||||||||||||
- Pros: Release before Ubuntu FF, Christmas week not affecting cycle
- Cons: Longer than 3 month
Cycle for C (3 months):
| 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 |
| BF | FF | GF | ||||||||
| Development (8 weeks) | QA | |||||||||
- Cons: Release after Ubuntu FinalFreeze
- Next ODS: week 20 or 21
Solution 2: Pure Three-month cycle from release to release
Cycle for Bexar (3 months):
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 |
| ODS | BF | FF | GF | |||||||||
| Prep | Development (8 weeks) | QA | ||||||||||
- Pros: True 3-month cycle
- Cons: Only 2 weeks of QA
Cycle for C (3 months):
| 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 |
| BF | FF | GF | |||||||||
| Development (9 weeks) | QA | ||||||||||
- Pros: Potential to sync dev summits
- Cons: Release after Ubuntu FinalFreeze
- Next ODS: week 19 or 20
Solution 2.1: The "Release C by Natty FinalFreeze" hypothesis
Cycle for Bexar (3- months):
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 |
| ODS | BF | FF | GF | |||||||||
| Prep | Development (8 weeks) | QA | ||||||||||
- Cons: Only 2 weeks of QA
Cycle for C (3- months):
| 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| BF | FF | GF | |||||||
| Development (8 weeks) | QA | ||||||||
- Pros: Release on Ubuntu FinalFreeze week
- Cons: Only two weeks of QA
- Next ODS: week 17 or 18
Solution 3: The "C is a 6-month cycle" hypothesis (sync with Ubuntu FF)
Cycle for Bexar (3+ months):
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 | 4 | 5 | 6 |
| ODS | BF | FF | GF | ||||||||||||
| Prep | Development (9 weeks) | QA | |||||||||||||
- Pros: Release the week before Ubuntu FF, Christmas week not affecting cycle
- Cons: Longer than 3 month
Cycle for C (6 months):
| 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20 | 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 |
| BF | FF | GF | RC | ||||||||||||||||||||
| Development (18 weeks) | QA | ||||||||||||||||||||||
- Pros: Release the week before Ubuntu FF
- Cons: Too long for a cycle without ODS
- Next ODS: week 34 or 35
Implementation
tbd
Test/Demo Plan
n/a
Unresolved issues
tbd
BoF agenda and discussion
tbd
