Create v1.34 release directory #2780
+153
−0
There are no files selected for viewing
This file contains hidden or 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
This file contains hidden or 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,15 @@ | ||
| # See the OWNERS docs at https://go.k8s.io/owners | ||
|
|
||
| approvers: | ||
| - Vyom-Yadav # v1.34 Release Team Lead | ||
| - fsmunoz # v1.34 Emeritus Advisor | ||
| - rytswd # v1.34 Release Team Lead Shadow | ||
| - wendy-ha18 # v1.34 Release Team Lead Shadow | ||
| - chanieljdan # v1.34 Release Team Lead Shadow | ||
| - sreeram-venkitesh # v1.34 Release Team Lead Shadow | ||
|
|
||
| reviewers: | ||
| - aibarbetta # v1.34 Communications Lead | ||
| - michellengnx # v1.34 Docs Lead | ||
| - jenshu # v1.34 Enhancements Lead | ||
| - Rajalakshmi-Girish # v1.34 Release Signal Lead |
This file contains hidden or 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,121 @@ | ||
| --- | ||
| title: "Kubernetes v1.34 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 v1.34 | ||
|
|
||
| #### Links | ||
|
|
||
| * [This document](https://git.k8s.io/sig-release/releases/release-1.34/README.md) | ||
| * [Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.34/release-team.md) | ||
| * [Meeting Minutes](https://bit.ly/k8s134-releasemtg) (members of [release-team@] receive meeting invites) | ||
| * [v1.34 Release Calendar](https://bit.ly/k8s-release-cal) | ||
| * Contact: [#sig-release](https://kubernetes.slack.com/archives/C2C40FMNF) on | ||
| slack, [release-team](mailto://[email protected]) on e-mail | ||
| * [Internal Contact Info](https://bit.ly/k8s134-contacts) (accessible only to members of [release-team@]) | ||
|
|
||
| #### Tracking docs | ||
|
|
||
| * [Enhancements Tracking Board](https://bit.ly/k8s134-enhancements) | ||
| * [Feature blog Tracking Board](https://bit.ly/k8s134-feature-blogs) | ||
| * [Bug Triage Tracking Board](https://bit.ly/k8s134-bugtriage) | ||
| * [CI Signal Project Board & Issue Tracking](https://bit.ly/k8s134-cisignal) | ||
| * [Retrospective Document](https://bit.ly/k8s134-retro) | ||
| * [kubernetes/kubernetes v1.34 milestone](https://github.com/kubernetes/kubernetes/milestone/67) | ||
|
|
||
| #### 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 v1.34 release cycle is as follows: | ||
|
|
||
| - **Monday 19th May 2025**: Week 1 — Release cycle begins | ||
| - **Thursday 12th June 2025**: | ||
| Week 4 — [Production Readiness Freeze][Production Readiness Freeze] | ||
| - **[21:00 UTC Friday 20th June 2025 / 14:00 PST Friday 20th June 2025](https://everytimezone.com/s/a17d0bdd)**: | ||
| Week 5 — [Enhancements Freeze][Enhancements Freeze] | ||
| - **[02:00 UTC Friday 11th July 2025 / 19:00 PST Thursday 10th July 2025](https://everytimezone.com/s/dcc4aad9)**: | ||
| Week 8 — [Feature blog freeze][Feature blog freeze] | ||
| - **[02:00 UTC Friday 25th July 2025 / 19:00 PDT Thursday 24th July 2025](https://everytimezone.com/s/a2c01c54)**: | ||
| Week 10 — [Code Freeze][Code Freeze] and [Test Freeze][Test Freeze] | ||
| - **Wednesday 6th August 2025**: Week 12 — [Docs Freeze][Docs Freeze] | ||
| - **Wednesday 27th August 2025**: Week 15 — Kubernetes v1.34.0 released | ||
|
|
||
| ## Timeline | ||
|
|
||
| | **What** | **Who** | **When** | **Week** | **Release Signal** | | ||
| |----------------------------------------------------------------------------------------|-------------------------------|-----------------------------------------------------------------------------------------------------------------|----------|--------------------------------------------------------------------------| | ||
| | Start of Release Cycle | Lead | Monday 19th May 2025 | week 1 | [master-blocking], [master-informing] | | ||
|
There was a problem hiding this comment. Perhaps it's worth adding a line before this to mention the shadow application form closes on 18th? There was a problem hiding this comment. This PR usually gets merged after the shadow application close, so I'm not sure about if this is consumable information for contributors. If we're adding closing date, we should also mention opening data, it would be something like: | [Shadow] Application Opens | Subproject Lead | Monday 5th May 2025 | week -2 |
| [Shadow] Application Closes | Subproject Lead | Sunday 18th May 2025 | week 0 | I think shadow program is more of a sig-release activity than being related to the release timeline. The release timeline imo serves contributors who are looking to get their changes merged in this release cycle. Still, if this feels like something that should be added, happy to discuss this further on Slack group chat. |
||
| | Start Enhancements Tracking | Enhancements Lead | Monday 19th May 2025 | week 1 | | | ||
| | Schedule finalized | Lead | Friday 23rd May 2025 | week 1 | | | ||
| | Team finalized | Lead | Friday 23rd May 2025 | week 1 | | | ||
| | Begin APAC-friendly meetings | Lead | Wednesday 28th May 2025 | week 2 | | | ||
| | Start Release Notes Draft | Docs Lead | Wednesday 4th June 2025 | week 3 | | | ||
| | v1.34.0-alpha.1 released | Branch Manager | Wednesday 11th June 2025 | week 4 | | | ||
|
There was a problem hiding this comment. LGTM from the branch management perspective schedule-wise. One minor issue I have on a single date (11th of June) but I will ask another BM to take over if I find myself completely not available on that day. |
||
| | **Begin [Production Readiness Freeze]** | Enhancements Lead | Thursday 12th June 2025 | week 4 | | | ||
| | **Begin [Enhancements Freeze]** | Enhancements Lead | [21:00 UTC Friday 20th June 2025 / 14:00 PST Friday 20th June 2025](https://everytimezone.com/s/a17d0bdd) | week 5 | | | ||
| | v1.34.0-alpha.2 released | Branch Manager | Wednesday 25th June 2025 | week 6 | | | ||
| | Docs deadline — Open placeholder PRs | Docs Lead | Thursday 3rd July 2025 | week 7 | | | ||
| | Call for [Exceptions][Exception] | Lead | Monday 7th July 2025 | week 8 | | | ||
| | Brace Yourself, Code Freeze is Coming | Comms / Release Signal | Monday 7th July 2025 | week 8 | | | ||
| | v1.34.0-alpha.3 released | Branch Manager | Wednesday 9th July 2025 | week 8 | | | ||
| | **Begin [Feature blog freeze] - Open placeholder PRs** | Comms Lead | [02:00 UTC Friday 11th July 2025 / 19:00 PST Thursday 10th July 2025](https://everytimezone.com/s/dcc4aad9) | week 8 | | | ||
| | v1.34.0-beta.0 released | Branch Manager | Wednesday 16th July 2025 | week 9 | | | ||
| | **Begin [Code Freeze] and [Test Freeze]** | Branch Manager | [02:00 UTC Friday 25th July 2025 / 19:00 PDT Thursday 24th July 2025](https://everytimezone.com/s/a2c01c54) | week 10 | | | ||
| | **Begin [Burndown]** (Monday, Wednesday, and Friday meetings) | Lead | Monday 28th July 2025 | week 11 | | | ||
| | Deprecations and Removals blog published | Comms | Monday 28th July 2025 | week 11 | | | ||
| | Docs deadline — PRs ready for review | Docs Lead | Tuesday 29th July 2025 | week 11 | | | ||
| | Release Highlights deadline | Comms | Tuesday 29th July 2025 | week 11 | | | ||
| | Burndown Meetings daily (Tuesday & Thursday over Slack) | Lead | Monday 4th August 2025 | week 12 | | | ||
| | release-1.34 branch created | Branch Manager | Wednesday 6th August 2025 | week 12 | | | ||
| | release-1.34 jobs created | Branch Manager | Wednesday 6th August 2025 | week 12 | | | ||
| | Start final draft of Release Notes | Docs Lead | Wednesday 6th August 2025 | week 12 | | | ||
| | **[Docs Freeze]** | Docs Lead | Wednesday 6th August 2025 | week 12 | | | ||
| | v1.34.0-rc.0 released | Branch Manager | Wednesday 6th August 2025 | week 12 | [1.34-informing], [1.34-blocking], [master-blocking], [master-informing] | | ||
| | Feature blogs ready to review | Enhancement Owner / SIG Leads | Friday 8th August 2025 | week 12 | | | ||
| | Release blog ready to review | Comms / Docs | [02:00 UTC Friday 15th August 2025 / 19:00 PDT Thursday 14th August 2025](https://everytimezone.com/s/815eefb6) | week 13 | | | ||
|
Comment on lines
+84
to
+85
There was a problem hiding this comment.
There was a problem hiding this comment. Thanks! For the Feature Blogs, we would want to have the deadline time defined for the Feature Blogs, so that it is clear for KEP authors. The actual blog review focus will be on the Release Announcement, and once that's in review, the Comms team should have some more time on reviewing the Feature Blogs. We want to ensure every blog authors have it done earlier than later, and thus "ready for review" deadline could happen on the same day in fact. I think the current timeline is fine as is, though. |
||
| | v1.34.0-rc.1 released | Branch Manager | Wednesday 20th August 2025 | week 14 | | | ||
| | Release Notes complete — reviewed & merged to https://github.com/kubernetes/kubernetes | Docs Lead | Wednesday 27th August 2025 | week 15 | | | ||
| | **v1.34.0 released** | Branch Manager | Wednesday 27th August 2025 | week 15 | | | ||
| | Release blog published | Comms | Wednesday 27th August 2025 | week 15 | | | ||
| | [Thaw] | Branch Manager | Wednesday 27th August 2025 | week 15 | | | ||
|
There was a problem hiding this comment. Can you add an extra entry one day after the release for Feature Blog publication start? |
||
| | Feature blog publication starts | Comms | Thursday 28th August 2025 | week 15 | | | ||
|
|
||
| ## Phases | ||
|
|
||
| Please refer to the [release phases document](../release_phases.md). | ||
|
|
||
| [Production Readiness Freeze]: ../release_phases.md#prr-freeze | ||
|
|
||
| [Enhancements Freeze]: ../release_phases.md#enhancements-freeze | ||
|
|
||
| [Burndown]: ../release_phases.md#burndown | ||
|
|
||
| [Code Freeze]: ../release_phases.md#code-freeze | ||
|
|
||
| [Exception]: ../release_phases.md#exceptions | ||
|
|
||
| [Thaw]: ../release_phases.md#thaw | ||
|
|
||
| [Test Freeze]: ../release_phases.md#test-freeze | ||
|
|
||
| [Docs Freeze]: ../release_phases.md#docs-freeze | ||
|
|
||
| [Feature blog freeze]: ../release_phases.md#feature-blog-freeze | ||
|
|
||
| [master-blocking]: https://testgrid.k8s.io/sig-release-master-blocking#Summary | ||
|
|
||
| [master-informing]: https://testgrid.k8s.io/sig-release-master-informing#Summary | ||
|
|
||
| [1.34-blocking]: https://testgrid.k8s.io/sig-release-1.34-blocking#Summary | ||
|
|
||
| [1.34-informing]: https://testgrid.k8s.io/sig-release-1.34-informing#Summary | ||
Oops, something went wrong.
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.
There is active conversation going on to replace the
bit.lylinks. These are kept as a placeholder and the links would be replaced with internal redirects (k8s.dev/go.k8s.io,TBD) by the time the release cycle starts.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.
The PR is open: https://kubernetes.slack.com/archives/C2C40FMNF/p1747315846937199, kubernetes/k8s.io#8109