Jump to: navigation, search

Difference between revisions of "StarlingX/Release Plan"

Line 21: Line 21:
  
 
=== Release cadence and Schedule ===
 
=== Release cadence and Schedule ===
 +
 
'''Releases are published in a time based fashion:'''
 
'''Releases are published in a time based fashion:'''
 
* Every Long Term period with quarterly updates.
 
* Every Long Term period with quarterly updates.
 
* Every Quarterly with monthly updates.
 
* Every Quarterly with monthly updates.
 +
 +
 +
'''Monthly release'''
 +
* Each month in the 2nd week of the month a branch will be pulled.
 +
* Branch name format stx.YY.MM.patch#
 +
  e.g. stx.2018.08.0x (where “0x” is a patch number)
 +
 +
 +
'''Quarterly release'''
 +
* 2nd month in the quarter.
 +
* For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter.
 +
 +
 +
'''Long Team release'''
 +
* '''TBD'''
 +
  
 
=== Support length ===
 
=== Support length ===
Line 32: Line 49:
 
* Visit the release team page
 
* Visit the release team page
  
−
[[File:Stx  Release Plan.png||]]
 
  
−
==Release Plan==
 
  
−
The community has decided to adapt the quarterly release cadence. We agreed to follow the time-based release process. If your code is ready, it gets released.  If it's not ready, you wait for the next release
 
  
−
We are going to support the quarterly release cadence using monthly branches.  The branches will be named "stx.<year>.<month>, for example "stx.2018.07" for the branch for July 2018.  We will be pulling branches monthly to allow the project's testing team to have a stable environment to run long duration tests.
+
[[File:Stx Release Plan.png||]]
−
 
 
−
Each quarter we will use the 2nd month's branch as the branch for the quarterly release.  The releases will be named "stx.<year>.<month>.<patch number>, with the patch number starting at zero and increasing with each new patch (fix) on the branch.  So the release for Q3 of 2018 will be named "stx.2018.08.0x", where "x" is the number of patches against that branch.  Note that the release is named after the month the branch was pulled in, not the month the release ships in.
 
−
 
 
−
The timeline for Q3 of 2018 looks like this:
 
−
Week of July 9th - pull stx.2018.07 branch for testing
 
−
Week of August 6th - pull stx.2018.08 branch as the Q3 release branch
 
−
Week of September 10th - pull stx.2018.09 branch for testing
 
−
 
 
−
Any defects found in a branch should be fixed on master. Fixes needed for a release or to unblock testing shall be cherry picked into the branch as needed.
 

Revision as of 21:22, 16 July 2018

Releases

List of releases

Current

Version Docs Release Date End of Life Date
Stx.08.2018.0x (Quarterly) Release Notes link TBD TBD + 6 months
...

Future

Version Docs Release Date End of Life Date
...

Management of releases

Release cadence and Schedule

Releases are published in a time based fashion:

  • Every Long Term period with quarterly updates.
  • Every Quarterly with monthly updates.


Monthly release

  • Each month in the 2nd week of the month a branch will be pulled.
  • Branch name format stx.YY.MM.patch# 
  e.g. stx.2018.08.0x (where “0x” is a patch number)


Quarterly release

  • 2nd month in the quarter.
  • For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter.


Long Team release

  • TBD


Support length

  • Quarterly releases are supported for 6 months.
  • Long Term releases are supported for ## years Long term link

Release team

  • Visit the release team page



Stx Release Plan.png

Retrieved from "https://wiki.openstack.org/w/index.php?title=StarlingX/Release_Plan&oldid=162805"