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. | ||
---- | ---- | ||
== List of releases == | == List of releases == | ||
| Line 18: | Line 20: | ||
| ... || || || | | ... || || || | ||
|} | |} | ||
| − | |||
| − | === Release | + | == Release Definition == |
| + | |||
| + | A StarlingX milestone/release is a 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.) | ||
| + | |||
| + | == Management of Releases == | ||
| + | |||
| + | === Release Cadence and Schedule === | ||
'''Releases are published in a time based fashion:''' | '''Releases are published in a time based fashion:''' | ||
| Line 26: | Line 38: | ||
* Every Quarterly with monthly updates. | * Every Quarterly with monthly updates. | ||
| − | + | '''Monthly Milestone Release''' | |
| − | '''Monthly | ||
* Each month in the 2nd week of the month a branch will be pulled. | * Each month in the 2nd week of the month a branch will be pulled. | ||
| − | * Branch name format stx | + | * Branch name format stx-YYYY.MM.nn |
| − | e.g. stx | + | e.g. stx-2018.08.nn (where “nn” is a sequence number) |
| − | |||
| − | '''Quarterly | + | '''Quarterly Release''' |
* 2nd month in the quarter. | * 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. | * For each quarterly release, the code freeze for that release is the 2nd week in the 2nd month in the quarter. | ||
| − | |||
'''Long Term release''' | '''Long Term release''' | ||
* '''TBD''' | * '''TBD''' | ||
| − | |||
=== Support length === | === Support length === | ||
Revision as of 20:29, 18 July 2018
Releases
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.
Contents
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 |
|---|---|---|---|
| ... |
Release Definition
A StarlingX milestone/release is a 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.)
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 Milestone Release
- Each month in the 2nd week of the month a branch will be pulled.
- Branch name format stx-YYYY.MM.nn
e.g. stx-2018.08.nn (where “nn” is a sequence 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 Term release
- TBD
Support length
- Quarterly releases are supported for 6 months.
- Long Term releases are out of plan so far.
Release team
- Intel CI/CD Lead - hazzim.i.anaya.casas@intel.com
- Intel Developer - mario.alfredo.c.arevalo@intel.com
