Skip to content
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 39 additions & 0 deletions docs/release/releases/release-1.13.md
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 |
Copy link
Member

@wendy-ha18 wendy-ha18 Nov 25, 2025

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.

| v1.13.0-beta.1 released | Release Lead | Tuesday 31st March 2026 | week 13 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

we don't know how many beta releases will actually happen (even though normally it will need only beta.1). Like previous schedules, I think we could put it generic v1.13.0-beta.x released.

| 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 |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| 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 |

Copy link
Member

@wendy-ha18 wendy-ha18 Nov 25, 2025

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.

| v1.13.0-rc.1 released | Release Lead | Tuesday 14th April 2026 | week 15 |
Copy link
Member

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.

| **v1.13.0 released** | Release Lead | Tuesday 21st April 2026 | week 16 |
| *v1.11.x & v1.12.x released* | Release Lead | Tuesday 21st April 2026 | week 16 |
| Organize release retrospective | Release Lead | TBC | week 16 |
| *v1.13.1 released (tentative)* | Release Lead | Tuesday 28th April 2026 | |

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).
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
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).

Copy link
Member

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.


## Release team

| **Role** | **Lead** (**GitHub / Slack ID**) | **Team member(s) (GitHub / Slack ID)** |
|-------------------------------------------|----------------------------------|----------------------------------------|
| Release Lead | TBD | |
| Communications/Docs/Release Notes Manager | TBD | |
| CI Signal/Bug Triage/Automation Manager | TBD | |
| Emeritus Advisor | TBD | |

Loading