Adding a release page under "Release Information"
This commit is contained in:
@@ -0,0 +1,195 @@
|
||||
---
|
||||
title: Patch Releases
|
||||
type: docs
|
||||
auto_generated: true
|
||||
---
|
||||
<!-- THIS CONTENT IS AUTO-GENERATED via ./scripts/update-release-info.sh in k/website -->
|
||||
|
||||
{{< warning >}}
|
||||
This content is auto-generated and links may not function. The source of the document is located [here](https://github.com/kubernetes/sig-release/blob/master/releases/patch-releases.md).
|
||||
{{< /warning >}}
|
||||
|
||||
# Kubernetes Patch Releases
|
||||
|
||||
Schedule and team contact information for Kubernetes patch releases.
|
||||
|
||||
For general information about Kubernetes release cycle, see the
|
||||
[release process description].
|
||||
|
||||
## Cadence
|
||||
|
||||
Our typical patch release cadence is monthly. It is
|
||||
commonly a bit faster (1 to 2 weeks) for the earliest patch releases
|
||||
after a 1.X minor release. Critical bug fixes may cause a more
|
||||
immediate release outside of the normal cadence. We also aim to not make
|
||||
releases during major holiday periods.
|
||||
|
||||
## Contact
|
||||
|
||||
See the [Release Managers page][release-managers] for full contact details on the Patch Release Team.
|
||||
|
||||
Please give us a business day to respond - we may be in a different timezone!
|
||||
|
||||
In between releases the team is looking at incoming cherry-pick
|
||||
requests on a weekly basis. The team will get in touch with
|
||||
submitters via GitHub PR, SIG channels in Slack, and direct messages
|
||||
in Slack and [email](mailto:release-managers-private@kubernetes.io)
|
||||
if there are questions on the PR.
|
||||
|
||||
## Cherry-Picks
|
||||
|
||||
Please follow the [cherry-pick process].
|
||||
|
||||
Cherry-picks must be merge-ready in GitHub with proper labels (eg:
|
||||
approved, lgtm, release note) and passing CI tests ahead of the
|
||||
cherry-pick deadline. This is typically two days before the target
|
||||
release, but may be more. Earlier PR readiness is better, as we
|
||||
need time to get CI signal after merging your cherry-picks ahead
|
||||
of the actual release.
|
||||
|
||||
Cherry-pick PRs which miss merge criteria will be carried over and tracked
|
||||
for the next patch release.
|
||||
|
||||
## Support Period
|
||||
|
||||
In accordance with the [yearly support KEP][yearly-support], the Kubernetes
|
||||
Community will support active patch release series for a period of roughly
|
||||
fourteen (14) months.
|
||||
|
||||
The first twelve months of this timeframe will be considered the standard
|
||||
period.
|
||||
|
||||
Towards the end of the twelve month, the following will happen:
|
||||
|
||||
- [Release Managers][release-managers] will cut a release
|
||||
- The patch release series will enter maintenance mode
|
||||
|
||||
During the two-month maintenance mode period, Release Managers may cut
|
||||
additional maintenance releases to resolve:
|
||||
|
||||
- CVEs (under the advisement of the Product Security Committee)
|
||||
- dependency issues (including base image updates)
|
||||
- critical core component issues
|
||||
|
||||
At the end of the two-month maintenance mode period, the patch release series
|
||||
will be considered EOL (end of life) and cherry picks to the associated branch
|
||||
are to be closed soon afterwards.
|
||||
|
||||
Note that the 28th of the month was chosen for maintenance mode and EOL target
|
||||
dates for simplicity (every month has it).
|
||||
|
||||
## Upcoming Monthly Releases
|
||||
|
||||
Timelines may vary with the severity of bug fixes, but for easier planning we
|
||||
will target the following monthly release points. Unplanned, critical
|
||||
releases may also occur in between these.
|
||||
|
||||
| Monthly Patch Release | Target date |
|
||||
| --- | --- |
|
||||
| May 2021 | 2021-05-12 |
|
||||
| June 2021 | 2021-06-16 |
|
||||
| July 2021 | 2021-07-14 |
|
||||
|
||||
## Detailed Release History for Active Branches
|
||||
|
||||
### 1.21
|
||||
|
||||
**1.21** enters maintenance mode on **2022-04-28**
|
||||
|
||||
End of Life for **1.21** is **2022-06-28**
|
||||
|
||||
| PATCH RELEASE | CHERRY PICK DEADLINE | TARGET DATE |
|
||||
|--- |--- |--- |
|
||||
| 1.21.1 | 2021-05-07 | 2021-05-12 |
|
||||
|
||||
### 1.20
|
||||
|
||||
**1.20** enters maintenance mode on **2021-12-28**
|
||||
|
||||
End of Life for **1.20** is **2022-02-28**
|
||||
|
||||
| PATCH RELEASE | CHERRY PICK DEADLINE | TARGET DATE |
|
||||
|--- |--- |--- |
|
||||
| 1.20.7 | 2021-05-07 | 2021-05-12 |
|
||||
| 1.20.6 | 2021-04-09 | 2021-04-14 |
|
||||
| 1.20.5 | 2021-03-12 | 2021-03-17 |
|
||||
| 1.20.4 | 2021-02-12 | 2021-02-18 |
|
||||
| 1.20.3 | [Conformance Tests Issue](https://groups.google.com/g/kubernetes-dev/c/oUpY9vWgzJo) | 2021-02-17 |
|
||||
| 1.20.2 | 2021-01-08 | 2021-01-13 |
|
||||
| 1.20.1 | [Tagging Issue](https://groups.google.com/g/kubernetes-dev/c/dNH2yknlCBA) | 2020-12-18 |
|
||||
|
||||
### 1.19
|
||||
|
||||
**1.19** enters maintenance mode on **2021-08-28**
|
||||
|
||||
End of Life for **1.19** is **2021-10-28**
|
||||
|
||||
| PATCH RELEASE | CHERRY PICK DEADLINE | TARGET DATE |
|
||||
|--- |--- |--- |
|
||||
| 1.19.11 | 2021-05-07 | 2021-05-12 |
|
||||
| 1.19.10 | 2021-04-09 | 2021-04-14 |
|
||||
| 1.19.9 | 2021-03-12 | 2021-03-17 |
|
||||
| 1.19.8 | 2021-02-12 | 2021-02-17 |
|
||||
| 1.19.7 | 2021-01-08 | 2021-01-13 |
|
||||
| 1.19.6 | [Tagging Issue](https://groups.google.com/g/kubernetes-dev/c/dNH2yknlCBA) | 2020-12-18 |
|
||||
| 1.19.5 | 2020-12-04 | 2020-12-09 |
|
||||
| 1.19.4 | 2020-11-06 | 2020-11-11 |
|
||||
| 1.19.3 | 2020-10-09 | 2020-10-14 |
|
||||
| 1.19.2 | 2020-09-11 | 2020-09-16 |
|
||||
| 1.19.1 | 2020-09-04 | 2020-09-09 |
|
||||
|
||||
### 1.18
|
||||
|
||||
**1.18** enters maintenance mode on **2021-04-28**
|
||||
|
||||
End of Life for **1.18** is **2021-05-12**
|
||||
|
||||
| PATCH RELEASE | CHERRY PICK DEADLINE | TARGET DATE |
|
||||
|--- |--- |--- |
|
||||
| 1.18.19 | 2021-05-07 | 2021-05-12 |
|
||||
| 1.18.18 | 2021-04-09 | 2021-04-14 |
|
||||
| 1.18.17 | 2021-03-12 | 2021-03-17 |
|
||||
| 1.18.16 | 2021-02-12 | 2021-02-17 |
|
||||
| 1.18.15 | 2021-01-08 | 2021-01-13 |
|
||||
| 1.18.14 | [Tagging Issue](https://groups.google.com/g/kubernetes-dev/c/dNH2yknlCBA) | 2020-12-18 |
|
||||
| 1.18.13 | 2020-12-04 | 2020-12-09 |
|
||||
| 1.18.12 | N/A | 2020-11-12 |
|
||||
| 1.18.11 | [No-op release](https://groups.google.com/g/kubernetes-dev/c/nJix1xLQvZE) | 2020-11-11 |
|
||||
| 1.18.10 | 2020-10-09 | 2020-10-14 |
|
||||
| 1.18.9 | 2020-09-11 | 2020-09-16 |
|
||||
| 1.18.8 | N/A | 2020-08-13 |
|
||||
| 1.18.7 | 2020-08-07 | 2020-08-12 |
|
||||
| 1.18.6 | 2020-07-10 | 2020-07-15 |
|
||||
| 1.18.5 | 2020-06-25 | 2020-06-26 |
|
||||
| 1.18.4 | 2020-06-12 | 2020-06-17 |
|
||||
| 1.18.3 | 2020-05-15 | 2020-05-20 |
|
||||
| 1.18.2 | 2020-04-13 | 2020-04-16 |
|
||||
| 1.18.1 | 2020-04-06 | 2020-04-08 |
|
||||
|
||||
## Non-Active Branch History
|
||||
|
||||
These releases are no longer supported.
|
||||
|
||||
| Minor Version | Final Patch Release | EOL date |
|
||||
| --- | --- | --- |
|
||||
| 1.17 | 1.17.17 | 2021-01-13 |
|
||||
| 1.16 | 1.16.15 | 2020-09-02 |
|
||||
| 1.15 | 1.15.12 | 2020-05-06 |
|
||||
| 1.14 | 1.14.10 | 2019-12-11 |
|
||||
| 1.13 | 1.13.12 | 2019-10-15 |
|
||||
| 1.12 | 1.12.10 | 2019-07-08 |
|
||||
| 1.11 | 1.11.10 | 2019-05-01 |
|
||||
| 1.10 | 1.10.13 | 2019-02-13 |
|
||||
| 1.9 | 1.9.11 | 2018-09-29 |
|
||||
| 1.8 | 1.8.15 | 2018-07-12 |
|
||||
| 1.7 | 1.7.16 | 2018-04-04 |
|
||||
| 1.6 | 1.6.13 | 2017-11-23 |
|
||||
| 1.5 | 1.5.8 | 2017-10-01 |
|
||||
| 1.4 | 1.4.12 | 2017-04-21 |
|
||||
| 1.3 | 1.3.10 | 2016-11-01 |
|
||||
| 1.2 | 1.2.7 | 2016-10-23 |
|
||||
|
||||
[cherry-pick process]: https://git.k8s.io/community/contributors/devel/sig-release/cherry-picks.md
|
||||
[release-managers]: /release-managers.md
|
||||
[release process description]: https://git.k8s.io/community/contributors/devel/sig-release/release.md
|
||||
[yearly-support]: https://git.k8s.io/enhancements/keps/sig-release/1498-kubernetes-yearly-support-period/README.md
|
||||
Reference in New Issue
Block a user