-
Notifications
You must be signed in to change notification settings - Fork 392
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Initial v1.31 docs #2494
Merged
Merged
Initial v1.31 docs #2494
Changes from 2 commits
Commits
Show all changes
4 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,12 @@ | ||
# See the OWNERS docs at https://go.k8s.io/owners | ||
|
||
approvers: | ||
- neoaggelos # 1.31 Release Team Lead | ||
- Priyankasaggu11929 # 1.31 Emeritus Advisor | ||
|
||
reviewers: | ||
- a-mccarthy # 1.31 Communications Lead | ||
- npolshakova # 1.31 Release Notes Lead | ||
- Princesso # 1.31 Docs Lead | ||
- sreeram-venkitesh # 1.31 Enhancements Lead | ||
- Vyom-Yadav # 1.31 Release Signal Lead |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,90 @@ | ||
--- | ||
title: "Kubernetes 1.31 Release Information" | ||
weight: 98 | ||
slug: "release" | ||
aliases: [ "/release" ] | ||
description: | | ||
Information regarding the current release cycle including important dates, | ||
Release Team contact information, tracking spreadsheets and more! | ||
--- | ||
|
||
# Kubernetes 1.31 | ||
|
||
|
||
#### Links | ||
|
||
* [This document](https://git.k8s.io/sig-release/releases/release-1.31/README.md) | ||
* [Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.31/release-team.md) | ||
* [Meeting Minutes](https://bit.ly/k8s131-releasemtg) (members of [release-team@] receive meeting invites) | ||
* [v1.31 Release Calendar](https://bit.ly/k8s-release-cal) | ||
* Contact: [#sig-release](https://kubernetes.slack.com/archives/C2C40FMNF) on slack, [release-team](mailto://release-team@kubernetes.io) on e-mail | ||
* [Internal Contact Info](https://bit.ly/k8s131-contacts) (accessible only to members of [release-team@]) | ||
|
||
#### Tracking docs | ||
|
||
* [Enhancements Tracking Board](https://github.com/orgs/kubernetes/projects/180/views/1) <!-- TODO: replace with bitly link --> | ||
* [Feature blog Tracking Board](https://github.com/orgs/kubernetes/projects/180/views/5) <!-- TODO: replace with bitly link --> | ||
* [Bug Triage Tracking Board](https://bit.ly/k8s131-bugtriage) | ||
* [CI Signal Project Board & Issue Tracking](https://bit.ly/k8s131-cisignal) | ||
* [Retrospective Document](https://bit.ly/k8s131-retro) | ||
* [kubernetes/sig-release v1.31 milestone](https://github.com/kubernetes/kubernetes/milestone/64) | ||
|
||
#### Guides | ||
|
||
* [Targeting Issues and PRs to This Milestone](https://git.k8s.io/community/contributors/devel/sig-release/release.md) | ||
* [Triaging and Escalating Test Failures](https://git.k8s.io/community/contributors/devel/sig-testing/testing.md#troubleshooting-a-failure) | ||
|
||
## Summary | ||
|
||
The 1.31 release cycle is as follows: | ||
|
||
- **Monday 27th May 2024**: Week 1 — Release cycle begins | ||
- **Thursday 20th June 2024**: Week 4 — [Production Readiness Freeze](https://groups.google.com/g/kubernetes-sig-architecture/c/a6_y81N49aQ) | ||
- **[02:00 UTC Friday 28th June 2024 / 19:00 PDT Thursday 27th June 2024](https://everytimezone.com/s/4967931f)**: Week 5 — [Enhancements Freeze](../release_phases.md#enhancements-freeze) | ||
- **[02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024](https://everytimezone.com/s/e9505237)**: Week 9 — [Code Freeze](../release_phases.md#code-freeze) | ||
- **[01:00 UTC Wednesday 14th August 2024 / 19:00 PDT Tuesday 13th August 2024](https://everytimezone.com/s/59e6cf02)**: Week 11 — [Test Freeze](../release_phases.md#test-freeze) | ||
- **Tuesday 13th August 2024**: Week 12 — [Docs Freeze](../release_phases.md#docs-freeze) | ||
- **Wednesday 4th September 2024**: Week 15 — Kubernetes v1.31.0 released | ||
|
||
## Timeline | ||
|
||
| **What** | **Who** | **When** | **Week** | **CI Signal** | | ||
| -------------------------------------------------------------------------------------- | ----------------------------- | ----------------------------------------------------------------------------------------------------------------- | -------- | ------------------------------------------------------ | | ||
| Start of Release Cycle | Lead | Monday 27th May 2024 | week 1 | [master-blocking] | | ||
| Start Enhancements Tracking | Enhancements Lead | Monday 27th May 2024 | week 1 | | | ||
| Schedule finalized | Lead | Friday 31st May 2024 | week 1 | | | ||
| Team finalized | Lead | Friday 31st May 2024 | week 1 | | | ||
| Start Release Notes Draft | Release Notes Lead | Tuesday 11th June 2024 | week 3 | | | ||
| 1.31.0-alpha.1 released | Branch Manager | Tuesday 18th June 2024 | week 4 | | | ||
| Production Readiness Freeze | Enhancements Lead | Thursday 20th June 2024 | week 4 | | | ||
| **Begin [Enhancements Freeze]** | Enhancements Lead | [02:00 UTC Friday 28th June 2024 / 19:00 PDT Thursday 27th June 2024](https://everytimezone.com/s/4967931f) | week 5 | [master-blocking], [master-informing] | | ||
| 1.31.0-alpha.2 released | Branch Manager | Tuesday 2nd July 2024 | week 6 | | | ||
| Docs deadline — Open placeholder PRs | Docs Lead | Thursday 11th July 2024 | week 7 | | | ||
| Begin Friday APAC-friendly meetings | Lead | Friday 12th July 2024 | week 7 | | | ||
| **Call for [Exceptions][Exception]** | Lead | Monday 15th July 2024 | week 8 | | | ||
| Brace Yourself, Code Freeze is Coming | Comms / Release Signal | Monday 15th July 2024 | week 8 | | | ||
| 1.31.0-alpha.3 released | Branch Manager | Tuesday 16th July 2024 | week 8 | | | ||
| **Begin Feature blog freeze** | Comms Lead | [02:00 UTC Wednesday 17th July 2024 / 19:00 PDT Tuesday 17th July 2024](https://everytimezone.com/s/ce9939f1) | week 8 | | | ||
| **Begin [Code Freeze]** | Branch Manager | [02:00 UTC Wednesday 24th July 2024 / 19:00 PDT Tuesday 23rd July 2024](https://everytimezone.com/s/e9505237) | week 9 | | | ||
| Deprecations and Removals blog published | Comms | Thursday 25th July 2024 | week 9 | | | ||
| **Preparing for Feature blogs review — Initiating outreach** | Comms | Monday 29th July 2024 | week 10 | | | ||
| 1.31.0-beta.0 released | Branch Manager | Tuesday 30th July 2024 | week 10 | | | ||
| Docs deadline — PRs ready for review | Docs Lead | Tuesday 30th July 2024 | week 10 | | | ||
| **Begin [Burndown]** (Monday, Wednesday, and Friday meetings) | Lead | Monday 5th August 2024 | week 11 | | | ||
| Major Themes deadline | Comms | Tuesday 6th August 2024 | week 11 | | | ||
| Start final draft of Release Notes | Release Notes Lead | Tuesday 6th August 2024 | week 11 | | | ||
| Release blog ready to review | Comms / Docs | [02:00 UTC Wednesday 7th August 2024 / 19:00 PDT Tuesday 6th August 2024](https://everytimezone.com/s/773523e6) | week 11 | | | ||
| Feature blogs ready to review | Enhancement Owner / SIG Leads | Friday 9th August 2024 | week 11 | | | ||
| Burndown Meetings daily (Tuesday & Thursday over Slack) | Lead | Monday 12th August 2024 | week 12 | | | ||
| **[Test Freeze]** | Branch Manager | [01:00 UTC Wednesday 14th August 2024 / 19:00 PDT Tuesday 13th August 2024](https://everytimezone.com/s/59e6cf02) | week 12 | | | ||
| release-1.31 branch created | Branch Manager | Tuesday 13th August 2024 | week 12 | | | ||
| release-1.31 jobs created | Branch Manager | Tuesday 13th August 2024 | week 12 | | | ||
| 1.31.0-rc.0 released | Branch Manager | Tuesday 13th August 2024 | week 12 | [1.31-blocking], [master-blocking], [master-informing] | | ||
| **Docs Freeze** | Docs Lead | Tuesday 13th August 2024 | week 12 | | | ||
| Major Themes complete | Release Notes Lead | Tuesday 20th August 2024 | week 13 | | | ||
| 1.31.0-rc.1 released | Branch Manager | Tuesday 20th August 2024 | week 13 | | | ||
| 1.31.0-rc.2 released | Branch Manager | Thursday 29th August 2024 | week 14 | [1.31-blocking], [master-blocking], [master-informing] | | ||
| Release Notes complete — reviewed & merged to https://github.com/kubernetes/kubernetes | Release Notes Lead | Wednesday 4th September 2024 | week 15 | | | ||
| **v1.31.0 released** | Branch Manager | Wednesday 4th September 2024 | week 15 | | | ||
| Release blog published | Comms | Wednesday 4th September 2024 | week 15 | | | ||
| **[Thaw]** | Branch Manager | Wednesday 4th September 2024 | week 15 | | |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,16 @@ | ||
# Kubernetes 1.31 Release Team | ||
|
||
| **Team/Role** | **Lead Name** (**GitHub / Slack ID**) | **Shadow Name(s) (GitHub / Slack ID)** | | ||
| ----------------- | ------------------------------------------------------------------------------------------------------------ | -------------------------------------- | | ||
| Release Team Lead | Angelos Kolaitis ([@neoaggelos](https://github.com/neoaggelos) / Slack : `@Angelos Kolaitis`) | | | ||
| Emeritus Adviser | Priyanka Saggu ([@Priyankasaggu11929](https://github.com/Priyankasaggu11929) / Slack: `@psaggu`) | N/A | | ||
| Enhancements | Sreeram Venkitesh ([@sreeram-venkitesh](https://github.com/sreeram-venkitesh) / Slack: `@sreeram.venkitesh`) | | | ||
| Release Notes | Nina Polshakova ([@npolshakova](https://github.com/npolshakova) / Slack: `@Nina Polshakova` ) | | | ||
| Communications | Abigail McCarthy ([@a-mccarthy](https://github.com/a-mccarthy) / Slack: `@abbie`) | | | ||
| Release Signal | Vyom Yadav ([@Vyom-Yadav](https://github.com/Vyom-Yadav) / Slack: `@Vyom Yadav` ) | | | ||
| Docs | Oluebube Princess Egbuna ([@Princesso](https://github.com/Princesso) / Slack: `@Bube`) | | | ||
| Branch Manager | TBD | TBD | | ||
|
||
Review the [Release Managers page](https://github.com/kubernetes/website/blob/main/content/en/releases/release-managers.md) for up-to-date contact information on Release Engineering personnel. | ||
|
||
The schedule for all patch releases can be found at [Patch Releases page](https://github.com/kubernetes/website/blob/main/content/en/releases/patch-releases.md). It will be updated to include 1.31, once the 1.31 release cycle concludes. |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about omitting
v1.31.0-rc.2
and shifting everything into the last week of August? This would give v1.32 one more week, which is already a short one due to holidays.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1 We definitely need to pull things in by at least a week please. All the previous 2nd release of the year were 1.22, 1.25, 128 were in August - looking at https://endoflife.date/kubernetes. If plan for Sep and we slip by a week that will make it hard for the last release of the year (fewer weeks there).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Alternatively can start a week earlier like we did in 1.28? https://github.com/kubernetes/sig-release/blob/fc1b3f7229ed78dccaf5271fb26c6c5c5b8b1feb/releases/release-1.28/README.md
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
+1, early-to-mid-August is where we've targeted in the past
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
for reference, here are historical release targets since 1.19 when we moved to 3 releases a year
The mid-year target release date has ranged from August 4th - August 25th, with an average of August 17th.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i've moved start to 20th may and release to august 22nd. @Priyankasaggu11929 do you think there would be enough time to handle the shadow applications if we started on the week of 13th may? I will be mostly unavailable during week 1, but we could still start I think
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Moving the start of the release to 20 May with a 22 August target for release is reasonable to me. That gives us enough time to run the shadow application and selection process, with a nice gap for 1.32. Pulling it any earlier than that will cut into shadow selection, but week 0 and week 1 are both so light for most teams it's doable if necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can send 1.31 shadow application form, as soon as tomorrow (May 1), run it for for 2 weeks (till May 15), and then announce/inform all applicants by May 22 at max.
So, starting as early as
AugustMay 13/14/15 should be fine IMO. We could then just use the first week to kick-off 1.31 enhancements opt-in, while we conclude selections.For sending out shadow application, I need a start date & tentative target release date, to inform applicants of their required time commitments.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do you mean starting May 13? I'm okay with that schedule, Week 1 doesn't have work for shadows (usually).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
thanks @neoaggelos @Priyankasaggu11929 @katcosgrove