-
Notifications
You must be signed in to change notification settings - Fork 1.4k
📖 Add Cluster API release-1.12 timeline document #12647
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
Merged
k8s-ci-robot
merged 2 commits into
kubernetes-sigs:main
from
mboersma:release-1.12-team
Aug 28, 2025
Merged
Changes from 1 commit
Commits
Show all changes
2 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 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,37 @@ | ||
| # Cluster API v1.12 | ||
|
|
||
| ## Timeline | ||
|
|
||
| The following table shows the preliminary dates for the `v1.12` release cycle. | ||
|
|
||
| | **What** | **Who** | **When** | **Week** | | ||
| |------------------------------------------------------|--------------|-----------------------------|----------| | ||
| | Start of Release Cycle | Release Lead | Monday 25th August 2025 | week 1 | | ||
| | Schedule finalized | Release Lead | Friday 29nd August 2025 | week 1 | | ||
| | Team finalized | Release Lead | Friday 29nd August 2025 | week 1 | | ||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 2nd September 2025 | week 2 | | ||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 7th October 2025 | week 7 | | ||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 4th November 2025 | week 11 | | ||
| | v1.11.0-beta.0 released | Release Lead | Tuesday 4th November 2025 | week 11 | | ||
| | Communicate beta to providers | Comms Lead | Tuesday 4th November 2025 | week 11 | | ||
| | Communicate upcoming code freeze to the community | Comms Lead | Tuesday 4th November 2025 | week 11 | | ||
| | KubeCon idle week | --- | --- | week 12 | | ||
| | v1.12.0-beta.x released | Release Lead | Tuesday 18th November 2025 | week 13 | | ||
| | release-1.12 branch created (**Begin Code Freeze**) | Release Lead | Tuesday 25th November 2025 | week 14 | | ||
| | v1.12.0-rc.0 released | Release Lead | Tuesday 25th November 2025 | week 14 | | ||
| | release-1.12 jobs created | Release Lead | Tuesday 25th November 2025 | week 14 | | ||
| | v1.12.0-rc.x released | Release Lead | Tuesday 2nd December 2025 | week 15 | | ||
| | **v1.12.0 released** | Release Lead | Tuesday 9th December 2025 | week 16 | | ||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 9th December 2025 | week 16 | | ||
| | Organize release retrospective | Release Lead | TBC | week 16 | | ||
| | *v1.12.1 released (tentative)* | Release Lead | Tuesday 16th December 2025 | | | ||
|
|
||
| After CAPI v1.12.0, the .1 release will follow up to add support for Kubernetes 1.35.0 when it becomes available. After .1, we expect to do monthly patch releases (more details will be provided in the 1.13 release schedule). | ||
|
|
||
| ## Release team | ||
|
|
||
| | **Role** | **Lead** (**GitHub / Slack ID**) | **Team member(s) (GitHub / Slack ID)** | | ||
| |-------------------------------------------|-------------------------------------------------------------------------------------------|----------------------------------------| | ||
| | Release Lead | TBD | TBD | | ||
| | Communications/Docs/Release Notes Manager | TBD | TBD | | ||
| | CI Signal/Bug Triage/Automation Manager | TBD | TBD | | ||
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.
Uh oh!
There was an error while loading. Please reload this page.