Jump to: navigation, search

Difference between revisions of "BexarReleaseScheduleSpec"

Line 47: Line 47:
 
=== Solution 1: Almost three-month cycle from summit to release ===
 
=== Solution 1: Almost three-month cycle from summit to release ===
  
−
Cycle for Bexar:
+
Cycle for Bexar (3+ months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 43  
 
|<width=80px>| 43  
Line 86: Line 86:
 
|}
 
|}
  
−
* Pros: release week before Ubuntu FF, Christmas week not affecting cycle
+
* Pros: Release before Ubuntu FF, Christmas week not affecting cycle
 
* Cons: Longer than 3 month
 
* Cons: Longer than 3 month
  
−
Cycle for C:
+
Cycle for C (3 months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 7  
 
|<width=80px>| 7  
Line 124: Line 124:
 
=== Solution 2: Pure Three-month cycle from release to release ===
 
=== Solution 2: Pure Three-month cycle from release to release ===
  
−
Cycle for Bexar:
+
Cycle for Bexar (3 months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 43  
 
|<width=80px>| 43  
Line 162: Line 162:
 
* Cons: Only 2 weeks of QA
 
* Cons: Only 2 weeks of QA
  
−
Cycle for C:
+
Cycle for C (3 months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 5  
 
|<width=80px>| 5  
Line 198: Line 198:
 
* Next ODS: week 19 or 20
 
* Next ODS: week 19 or 20
  
−
=== Solution 2.1: The "release C by Natty [[FinalFreeze]]" hypothesis ===
+
=== Solution 2.1: The "Release C by Natty [[FinalFreeze]]" hypothesis ===
  
−
Cycle for Bexar:
+
Cycle for Bexar (3- months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 43  
 
|<width=80px>| 43  
Line 237: Line 237:
 
* Cons: Only 2 weeks of QA
 
* Cons: Only 2 weeks of QA
  
−
Cycle for C:
+
Cycle for C (3- months):
 
{| border="1" cellpadding="2" cellspacing="0"
 
{| border="1" cellpadding="2" cellspacing="0"
 
|<width=80px>| 5  
 
|<width=80px>| 5  
Line 269: Line 269:
 
* Next ODS: week 17 or 18
 
* Next ODS: week 17 or 18
  
−
=== Solution 3: The "C is a 6-month cycle" hypothesis ===
+
=== Solution 3: The "C is a 6-month cycle" hypothesis (sync with Ubuntu FF) ===
  
−
tbc
+
Cycle for Bexar (3+ months):
 +
{| border="1" cellpadding="2" cellspacing="0"
 +
|<width=80px>| 43
 +
|<width=80px>| 44
 +
|<width=80px>| 45
 +
|<width=80px>| 46
 +
|<width=80px>| 47
 +
|<width=80px>| 48
 +
|<width=80px>| 49
 +
|<width=80px>| 50
 +
|<width=80px>| 51
 +
|<width=80px>| 52
 +
|<width=80px>| 1
 +
|<width=80px>| 2
 +
|<width=80px>| 3
 +
|<width=80px>| 4
 +
|<width=80px>| 5
 +
|<width=80px>| 6
 +
|-
 +
| 
 +
| 
 +
|  ODS
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
|  BF
 +
|  FF
 +
| 
 +
| 
 +
|  GF
 +
| 
 +
|-
 +
|colspan="3" | Prep
 +
|colspan="9" | Development (9 weeks)
 +
|colspan="4" | QA
 +
|}
 +
 
 +
* Pros: Release the week before Ubuntu FF, Christmas week not affecting cycle
 +
* Cons: Longer than 3 month
 +
 
 +
Cycle for C (6 months):
 +
{| border="1" cellpadding="2" cellspacing="0"
 +
|<width=80px>| 8
 +
|<width=80px>| 9
 +
|<width=80px>| 10
 +
|<width=80px>| 11
 +
|<width=80px>| 12
 +
|<width=80px>| 13
 +
|<width=80px>| 14
 +
|<width=80px>| 15
 +
|<width=80px>| 16
 +
|<width=80px>| 17
 +
|<width=80px>| 18
 +
|<width=80px>| 19
 +
|<width=80px>| 20
 +
|<width=80px>| 21
 +
|<width=80px>| 22
 +
|<width=80px>| 23
 +
|<width=80px>| 24
 +
|<width=80px>| 25
 +
|<width=80px>| 26
 +
|<width=80px>| 27
 +
|<width=80px>| 28
 +
|<width=80px>| 29
 +
|<width=80px>| 30
 +
|<width=80px>| 31
 +
|-
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
| 
 +
|  BF
 +
| 
 +
|  FF
 +
| 
 +
| 
 +
| 
 +
|  GF
 +
| 
 +
|  RC
 +
|-
 +
|colspan="18" | Development (18 weeks)
 +
|colspan="6" | QA
 +
|}
 +
 
 +
* Pros: Release the week before Ubuntu FF
 +
* Cons: Too long for a cycle without ODS
 +
* Next ODS: week 34 or 35
  
 
== Implementation ==
 
== Implementation ==

Revision as of 12:36, 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 (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

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