Jump to: navigation, search

Difference between revisions of "BexarReleaseScheduleSpec"

Line 45: Line 45:
 
* RC: Release Candidate on Tuesday. Release on Thursday. Acts of god are required to change the RC.
 
* 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 ===
+
=== Solution 1: Almost three-month cycle from summit to release ===
  
 
Cycle for Bexar:
 
Cycle for Bexar:
Line 64: Line 64:
 
|<width=80px>| 4  
 
|<width=80px>| 4  
 
|<width=80px>| 5  
 
|<width=80px>| 5  
−
|<width=80px>| 6
 
 
|-
 
|-
 
|   
 
|   
 
|   
 
|   
 
|  ODS  
 
|  ODS  
−
| 
 
 
|   
 
|   
 
|   
 
|   
Line 84: Line 82:
 
|-
 
|-
 
|colspan="3" | Prep  
 
|colspan="3" | Prep  
−
|colspan="10" | Development (10 weeks)  
+
|colspan="9" | Development (9 weeks)  
 
|colspan="3" | QA  
 
|colspan="3" | QA  
 
|}
 
|}
Line 93: Line 91:
 
Cycle for C:
 
Cycle for C:
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 +
|<width=80px>| 7
 
|<width=80px>| 8  
 
|<width=80px>| 8  
 
|<width=80px>| 9  
 
|<width=80px>| 9  
Line 103: Line 102:
 
|<width=80px>| 16  
 
|<width=80px>| 16  
 
|<width=80px>| 17  
 
|<width=80px>| 17  
−
|<width=80px>| 18
 
−
|<width=80px>| 19
 
 
|-
 
|-
−
| 
 
 
|   
 
|   
 
|   
 
|   
Line 119: Line 115:
 
|  GF  
 
|  GF  
 
|-
 
|-
−
|colspan="9" | Development (9 weeks)  
+
|colspan="8" | Development (8 weeks)  
 
|colspan="3" | QA  
 
|colspan="3" | QA  
 
|}
 
|}
  
−
* Cons: Release crunch at the same time as UDS
+
* Cons: Release after Ubuntu [[FinalFreeze]]
−
* Next ODS: week 22 or 23
+
* Next ODS: week 20 or 21
  
 
=== Solution 2: Pure Three-month cycle from release to release ===
 
=== Solution 2: Pure Three-month cycle from release to release ===
Line 147: Line 143:
 
|   
 
|   
 
|  ODS  
 
|  ODS  
 +
| 
 
|   
 
|   
 
|   
 
|   
Line 154: Line 151:
 
|  BF  
 
|  BF  
 
|  FF  
 
|  FF  
−
| 
 
 
|   
 
|   
 
|  GF  
 
|  GF  
 
|-
 
|-
 
|colspan="3" | Prep  
 
|colspan="3" | Prep  
−
|colspan="7" | Development (7 weeks)  
+
|colspan="8" | Development (8 weeks)  
−
|colspan="3" | QA  
+
|colspan="2" | QA  
 
|}
 
|}
  
 
* Pros: True 3-month cycle
 
* Pros: True 3-month cycle
−
* Cons: Only 7 weeks development time, Merging week falls on week 52
+
* Cons: Only 2 weeks of QA
  
 
Cycle for C:
 
Cycle for C:
Line 202: Line 198:
 
* Next ODS: week 19 or 20
 
* Next ODS: week 19 or 20
  
−
=== Solution 3: Adapted "short QA" cycles ===
+
=== Solution 2.1: The "release C by Natty [[FinalFreeze]]" hypothesis ===
  
 
Cycle for Bexar:
 
Cycle for Bexar:
Line 239: Line 235:
 
|}
 
|}
  
−
* Pros: Christmas week not affecting cycle
 
 
* Cons: Only 2 weeks of QA
 
* Cons: Only 2 weeks of QA
  
Line 271: Line 266:
  
 
* Pros: Release on Ubuntu [[FinalFreeze]] week
 
* Pros: Release on Ubuntu [[FinalFreeze]] week
−
* Cons: Relatively short cycle, only two weeks of QA
+
* Cons: Only two weeks of QA
 
* Next ODS: week 17 or 18
 
* Next ODS: week 17 or 18
 +
 +
=== Solution 3: The "C is a 6-month cycle" hypothesis ===
 +
 +
tbc
  
 
== Implementation ==
 
== Implementation ==

Revision as of 08:28, 5 November 2010

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:

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 week before Ubuntu FF, Christmas week not affecting cycle
  • Cons: Longer than 3 month

Cycle for C:

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:

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:

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:

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:

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

tbc

Implementation

tbd

Test/Demo Plan

n/a

Unresolved issues

tbd

BoF agenda and discussion

tbd

Retrieved from "https://wiki.openstack.org/w/index.php?title=BexarReleaseScheduleSpec&oldid=12406"