Jump to: navigation, search

Difference between revisions of "StarlingX/Release Plan"

Line 1: Line 1:
 
<big><big> '''Releases''' </big></big>
 
<big><big> '''Releases''' </big></big>
  
StarlingX is released periodically (currently every three months) with monthly milestone releases in between.  A release consists of a branch in the source code repositories that enables repeatable builds over time.
+
StarlingX is released periodically; one release in 2018 and three releases/year starting in 2019.  A release consists of a branch in the source code repositories that enables repeatable builds over time.
 
----
 
----
== List of releases ==
+
== List of Releases ==
'''Current'''
+
'''Planned'''
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Version !! Docs !! Release Date !! End of Life Date
+
! Version !! Code Freeze !! Release Date !! End of Life Date !! Docs
 
|-
 
|-
| 2018.07.0 || Release Notes link || 2018/07/20 || TBD + 6 months
+
| 2018.10.0 || 2018/09/26 || 2018/10/24 || TBD || TBD
 
|-
 
|-
| ... || || ||  
+
| 2019.03.0 || 2019/02/13 || 2018/03/13 || TBD || TBD
|}
+
|-
'''Future'''
+
| 2019.07.0 || TBD || TBD || TBD || TBD
{| class="wikitable"
 
 
|-
 
|-
! Version !! Docs !! Release Date !! End of Life Date
+
| 2019.11.0 || TBD || TBD || TBD || TBD
 
|-
 
|-
 
| ... ||  ||  ||  
 
| ... ||  ||  ||  
 
|}
 
|}
 +
  
 
== Release Definition ==
 
== Release Definition ==
Line 29: Line 29:
 
* will be maintained in the canonical repositories for a specified minimum period
 
* will be maintained in the canonical repositories for a specified minimum period
 
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
 
* The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
* The actual release is a tag on the corresponding branch, ie m/2018.07 milestone branch will be initially tagged as 2018.07.0
+
* The actual release is a tag on the corresponding branch, i.e. r/2018.10 release branch will be initially tagged as 2018.10.0
  
 
== Management of Releases ==
 
== Management of Releases ==
Line 36: Line 36:
  
 
'''Releases are published in a time based fashion:'''
 
'''Releases are published in a time based fashion:'''
* Every Long Term period with quarterly updates.
+
* The initial StarlingX release is planned for October 2018
* Every Quarterly with monthly updates.
+
* From 2019, the regular release cadence is 3 releases/year; released in March, July, and November.
  
==== Monthly Milestone ====
+
==== Formal Releases ====
 +
* Released three times per year
 +
* For each release, the code freeze for that release is four weeks prior to the release date.
 +
* Branch name format r/YYYY.MM[.n]
 +
** 'r/' is the branch name prefix (release)
 +
** .n is a sequence number appended if more than one branch is created in a given month
 +
r/2018.10
 +
* Release is tagged as YYYY.MM.0
  
* Each month in the 2nd week of the month a branch will be pulled.
+
==== Monthly Milestones ====
 +
* Informal milestones to be used by the test team for a pre-defined sanity/regression test cycle.
 +
* Created each month in the 2nd week of the month a branch will be pulled.
 
* Branch name format m/YYYY.MM[.n]
 
* Branch name format m/YYYY.MM[.n]
 
** 'm/' is the branch name prefix (milestone)
 
** 'm/' is the branch name prefix (milestone)
Line 48: Line 57:
 
* Release is tagged as YYYY.MM.0
 
* Release is tagged as YYYY.MM.0
  
==== Quarterly Release ====
+
==== Long Term Support ====
 
+
* To be defined based on release content, not time based
* 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.
 
* Branch name format r/YYYY.MM[.n]
 
** 'r/' is the branch name prefix (release)
 
** .n is a sequence number appended if more than one branch is created in a given month
 
r/2018.07
 
* Release is tagged as YYYY.MM.0
 
 
 
==== Long Term Release ====
 
 
 
* '''TBD'''
 
 
 
=== Support length ===
 
* Quarterly releases are supported for 6 months.
 
* Long Term releases are out of plan so far.
 
  
== Release team ==
+
=== Support Length ===
 +
* Formal releases are supported for 8 months; support for the '''n''' and '''n-1''' releases.
 +
* Long Term Support is ""TBD""
  
 +
== Release Team ==
 +
* Team Lead - ghada.khalil@windriver.com
 
* Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
 
* Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
 
* Intel Developer - mario.alfredo.c.arevalo@intel.com
 
* Intel Developer - mario.alfredo.c.arevalo@intel.com
 +
* For more information, visit the Releases sub-project wiki page [https://wiki.openstack.org/wiki/StarlingX/Releases here]
  
 +
== Release Diagram ==
 +
'''''Diagram needs to be updated'''''
 
[[File:Stx  Release Plan.png||]]
 
[[File:Stx  Release Plan.png||]]

Revision as of 11:14, 7 August 2018

Releases

StarlingX is released periodically; one release in 2018 and three releases/year starting in 2019. A release consists of a branch in the source code repositories that enables repeatable builds over time.


List of Releases

Planned

Version Code Freeze Release Date End of Life Date Docs
2018.10.0 2018/09/26 2018/10/24 TBD TBD
2019.03.0 2019/02/13 2018/03/13 TBD TBD
2019.07.0 TBD TBD TBD TBD
2019.11.0 TBD TBD TBD TBD
...


Release Definition

A StarlingX milestone/release is a tagged branch in the source code repositories that:

  • is considered stable and can be used for repeatable builds
  • will have no additional features added
  • will backport bug fixes for critical issues only
  • will be maintained in the canonical repositories for a specified minimum period
  • The list of repos included is maintained in stx-manifest/default.xml (or similar) for any given release. (Note: this file included non-StarlingX-managed repos, only repos from the "starlingx" and "stx-staging" remotes are included.)
  • The actual release is a tag on the corresponding branch, i.e. r/2018.10 release branch will be initially tagged as 2018.10.0

Management of Releases

Release Cadence and Schedule

Releases are published in a time based fashion:

  • The initial StarlingX release is planned for October 2018
  • From 2019, the regular release cadence is 3 releases/year; released in March, July, and November.

Formal Releases

  • Released three times per year
  • For each release, the code freeze for that release is four weeks prior to the release date.
  • Branch name format r/YYYY.MM[.n]
    • 'r/' is the branch name prefix (release)
    • .n is a sequence number appended if more than one branch is created in a given month
r/2018.10
  • Release is tagged as YYYY.MM.0

Monthly Milestones

  • Informal milestones to be used by the test team for a pre-defined sanity/regression test cycle.
  • Created each month in the 2nd week of the month a branch will be pulled.
  • Branch name format m/YYYY.MM[.n]
    • 'm/' is the branch name prefix (milestone)
    • .n is a sequence number appended if more than one branch is created in a given month
m/2018.07
  • Release is tagged as YYYY.MM.0

Long Term Support

  • To be defined based on release content, not time based

Support Length

  • Formal releases are supported for 8 months; support for the n and n-1 releases.
  • Long Term Support is ""TBD""

Release Team

  • Team Lead - ghada.khalil@windriver.com
  • Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
  • Intel Developer - mario.alfredo.c.arevalo@intel.com
  • For more information, visit the Releases sub-project wiki page here

Release Diagram

Diagram needs to be updated Stx Release Plan.png