istio
/
istio.io
mirror of https://github.com/istio/istio.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update release cadence doc (#5600) 

This info was outdated
This commit is contained in:
Istio Automation 2019-11-11 11:41:54 -08:00 committed by GitHub
parent 31d4b56b22
commit 20875b2be3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 8 additions and 21 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

29
content/en/about/release-cadence/index.md
View File

@ -5,32 +5,26 @@ weight: 15
icon: cadence
---
We produce new builds of Istio on a daily basis. Around once a month or so, we take one of these daily
builds and run it through a number of additional qualification tests and tag the build as a Snapshot release.
Around once a quarter or so, we take one of these Snapshot releases, run through a bunch more tests
and tag the build as a Long Term Support (LTS) release. Finally, if we find something wrong with an
We produce new builds of Istio for each commit. Around once a quarter or so, we build a Long Term Support (LTS) release,
and run through a bunch more tests and release qualification. Finally, if we find something wrong with an
LTS release, we issue patches.
The different types (Daily, Snapshot, LTS) represent different product quality levels and different levels of support
The different types represent different product quality levels and different levels of support
from the Istio team. In this context, *support* means that we will produce patch releases for critical issues and
offer technical assistance. Separately, 3rd parties and partners may offer longer-term support solutions.
|Type | Support Level | Quality and Recommended Use
|-----------------|----------------------------------------------------------|----------------------------
|Daily Build | No support | Dangerous, may not be fully reliable. Useful to experiment with.
|Snapshot Release | Support is provided for the latest snapshot release only | Expected to be quite stable, but use in production should be limited to an as-needed basis. Usually only adopted by bleeding edge users, or users seeking specific features.
|Development Build| No support | Dangerous, may not be fully reliable. Useful to experiment with.
|LTS Release | Support is provided until 3 months after the next LTS | Safe to deploy in production. Users are encouraged to upgrade to these releases as soon as possible.
|Patches | Same as the corresponding Snapshot/LTS release | Users are encouraged to adopt patch releases as soon as they are available for a given release.
You can find available releases on the [releases page](https://github.com/istio/istio/releases),
and if you're the adventurous type, you can learn about our daily builds on the [daily builds wiki](https://github.com/istio/istio/wiki/Daily-builds).
and if you're the adventurous type, you can learn about our development builds on the [development builds wiki](https://github.com/istio/istio/wiki/Dev%20Builds).
You can find high-level releases notes for each LTS release [here](/news).
## Naming scheme
Prior to Istio 0.8, we increased the product's version number on a monthly basis. Effective with 0.8,
we will increase the product's version number only for LTS releases.
Our naming scheme for LTS releases is:
{{< text plain >}}
@ -43,15 +37,8 @@ current LTS release. A patch is usually a small change relative to the LTS.
For snapshot releases, our naming scheme is:
{{< text plain >}}
<major>.<minor>.0-snapshot.<snapshot count>
<major>.<minor>-alpha.<sha>
{{< /text >}}
where `<major>.<minor>.0` represent the next LTS, and
`<snapshot count>` starts at 0 and increases for every snapshot leading up to the
next LTS.
In the unlikely event we need to issue a patch to a snapshot, it is numbered as:
{{< text plain >}}
<major>.<minor>.0-snapshot.<snapshot count>.<snapshot patch level>
{{< /text >}}
where `<major>.<minor>` represent the next LTS, and
`<sha>` represents the git commit the release is built from.