📖 Add Cluster API release-1.12 timeline document #12647
+37
−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
| 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 18th August 2025 | week 1 | | ||||||
| | Schedule finalized | Release Lead | Friday 22nd August 2025 | week 1 | | ||||||
| | Team finalized | Release Lead | Friday 22nd August 2025 | week 1 | | ||||||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 9th September 2025 | week 4 | | ||||||
|
There was a problem hiding this comment.
Suggested change
According to https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/releases/release-1.11.md we have to release 1.11.1 the Nov 2nd (~1 week after K8s 1.34 GA). There was a problem hiding this comment.
Fixed, thanks |
||||||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 7th October 2025 | week 8 | | ||||||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 4th November 2025 | week 12 | | ||||||
| | v1.12.0-beta.0 released | Release Lead | Tuesday 4th November 2025 | week 12 | | ||||||
| | Communicate beta to providers | Comms Lead | Tuesday 4th November 2025 | week 12 | | ||||||
| | Communicate upcoming code freeze to the community | Comms Lead | Tuesday 4th November 2025 | week 12 | | ||||||
| | KubeCon idle week | --- | --- | week 13 | | ||||||
| | v1.12.0-beta.x released | Release Lead | Tuesday 18th November 2025 | week 14 | | ||||||
| | release-1.12 branch created (**Begin Code Freeze**) | Release Lead | Tuesday 25th November 2025 | week 15 | | ||||||
| | v1.12.0-rc.0 released | Release Lead | Tuesday 25th November 2025 | week 15 | | ||||||
| | release-1.12 jobs created | Release Lead | Tuesday 25th November 2025 | week 15 | | ||||||
| | v1.12.0-rc.x released | Release Lead | Tuesday 2nd December 2025 | week 16 | | ||||||
| | **v1.12.0 released** | Release Lead | Tuesday 9th December 2025 | week 17 | | ||||||
| | *v1.10.x & v1.11.x released* | Release Lead | Tuesday 9th December 2025 | week 17 | | ||||||
| | Organize release retrospective | Release Lead | TBC | week 17 | | ||||||
| | *v1.12.1 released (tentative)* | Release Lead | Tuesday 16th December 2025 | week 18 | | ||||||
|
There was a problem hiding this comment. nit
Suggested change
I would prefer to not give the impression that this week is part of the release cycle, because it is already after GA |
||||||
|
|
||||||
| After the .0 the .1 release will be created to ensure faster Kubernetes support after K8s 1.35.0 will be available. After the .1 we expect to release monthly patch release (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.
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.
Let's move the start of the cycle to next week (I think it is more correct, considering GA was this week)
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.
Note: this will require to change week numbers in all the following lines 😅