-
Notifications
You must be signed in to change notification settings - Fork 1.4k
📖 Add v1.13 release schedule #13043
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
📖 Add v1.13 release schedule #13043
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -0,0 +1,39 @@ | ||||||
| # Cluster API v1.13 | ||||||
|
|
||||||
| ## Timeline | ||||||
|
|
||||||
| The following table shows the preliminary dates for the `v1.13` release cycle. | ||||||
|
|
||||||
| | **What** | **Who** | **When** | **Week** | | ||||||
| |------------------------------------------------------|--------------|-----------------------------|----------| | ||||||
| | Start of Release Cycle | Release Lead | Monday 5th January 2026 | week 1 | | ||||||
| | Schedule finalized | Release Lead | Friday 9th January 2026 | week 1 | | ||||||
| | Team finalized | Release Lead | Friday 9th January 2026 | week 1 | | ||||||
| | *v1.11.x & v1.12.x released* | Release Lead | Tuesday 20th January 2026 | week 3 | | ||||||
| | *v1.11.x & v1.12.x released* | Release Lead | Tuesday 17th February 2026 | week 7 | | ||||||
| | *v1.11.x & v1.12.x released* | Release Lead | Tuesday 17th March 2026 | week 11 | | ||||||
| | v1.13.0-beta.0 released | Release Lead | Tuesday 17th March 2026 | week 11 | | ||||||
| | Communicate beta to providers | Comms Lead | Tuesday 17th March 2026 | week 11 | | ||||||
| | Communicate upcoming code freeze to the community | Comms Lead | Tuesday 17th March 2026 | week 11 | | ||||||
| | KubeCon idle week | --- | --- | week 12 | | ||||||
| | v1.13.0-beta.1 released | Release Lead | Tuesday 31st March 2026 | week 13 | | ||||||
|
||||||
| | release-1.13 branch created (**Begin Code Freeze**) | Release Lead | Tuesday 7th April 2026 | week 14 | | ||||||
| | v1.13.0-rc.0 released | Release Lead | Tuesday 7th April 2026 | week 14 | | ||||||
| | release-1.13 jobs created | Release Lead | Tuesday 7th April 2026 | week 14 | | ||||||
|
||||||
| | release-1.13 jobs created | Release Lead | Tuesday 7th April 2026 | week 14 | | |
| | release-1.13 jobs created | CI Lead | Tuesday 7th April 2026 | week 14 | |
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.
According to role handbooks, the set up job should be the task of CI Lead. However, in CAPI v1.10-v1.11, it was assigned to CI Lead, but in v1.12, it was assigned back to Release Lead. We properly need to ask advice from maintainers to decide this one but I think it should be task of CI Lead.
Outdated
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.
Similarly, this could be v1.13.0-rc.x released.
Outdated
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.
| After CAPI v1.13.0, the .1 release will follow up to add support for Kubernetes 1.36.0 when it becomes available. After .1, we expect to do monthly patch releases (more details will be provided in the 1.14 release schedule). | |
| After CAPI v1.13.0, the .1 release will follow up to add support for Kubernetes v1.36.0 when it becomes available. After .1, we expect to do monthly patch releases (more details will be provided in the v1.14 release schedule). |
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.
Just thought since this release schedule we should use v before release versions for consistency.
Uh oh!
There was an error while loading. Please reload this page.
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.
[Optional] As a few old schedules have noted time for KubeCon, we can add KubeCon EU here 23-26 March 2026.