BexarReleaseScheduleSpec
Revision as of 08:12, 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.
Proposal 1: Three-month cycle from summit to release
Cycle for Bexar:
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 | 4 | 5 | 6 |
| ODS | BF | FF | GF | ||||||||||||
| Prep | Development (10 weeks) | QA | |||||||||||||
- Pros: release week before Ubuntu FF, Christmas week not affecting cycle
- Cons: Longer than 3 month
Cycle for C:
| 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 |
| BF | FF | GF | |||||||||
| Development (9 weeks) | QA | ||||||||||
- Cons: Release crunch at the same time as UDS
- Next ODS: week 22 or 23
Solution 2: Pure Three-month cycle from release to release
Cycle for Bexar:
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 |
| ODS | BF | FF | GF | |||||||||
| Prep | Development (7 weeks) | QA | ||||||||||
- Pros: True 3-month cycle
- Cons: Only 7 weeks development time, Merging week falls on week 52
Cycle for C:
| 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 3: Adapted "short QA" cycles
Cycle for Bexar:
| 43 | 44 | 45 | 46 | 47 | 48 | 49 | 50 | 51 | 52 | 1 | 2 | 3 |
| ODS | BF | FF | GF | |||||||||
| Prep | Development (8 weeks) | QA | ||||||||||
- Pros: Christmas week not affecting cycle
- Cons: Only 2 weeks of QA
Cycle for C:
| 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 |
| BF | FF | GF | |||||||
| Development (8 weeks) | QA | ||||||||
- Pros: Release on Ubuntu FinalFreeze week
- Cons: Relatively short cycle, only two weeks of QA
- Next ODS: week 17 or 18
Implementation
tbd
Test/Demo Plan
n/a
Unresolved issues
tbd
BoF agenda and discussion
tbd
