Skip to content

📖 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.

Sign up for GitHub

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

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

📖 Add v1.13 release schedule #13043

wants to merge 1 commit into from
+39 −0

Conversation

@pratik-mahalle
Copy link
Contributor

@pratik-mahalle pratik-mahalle commented Nov 25, 2025 •
edited
Loading

What this PR does / why we need it:
This PR adds the release schedule for Cluster API v1.13.

Which issue(s) this PR fixes:
Fixes #

/area documentation

@pratik-mahalle
add the release v1.13 timeline
bd1f06a 
Signed-off-by: Pratik Mahalle <[email protected]>
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 25, 2025

@pratik-mahalle: The label(s) area/release-eng cannot be applied, because the repository doesn't have them.

In response to this:

What this PR does / why we need it:
This PR adds the release schedule for Cluster API v1.13.

Which issue(s) this PR fixes:
Fixes #

/area documentation
/area release-eng

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the area/documentation Issues or PRs related to documentation label Nov 25, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 25, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign chrischdi for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 25, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 25, 2025

Hi @pratik-mahalle. Thanks for your PR.

I'm waiting for a github.com member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Nov 25, 2025
aman4433
aman4433 reviewed Nov 25, 2025
View reviewed changes
Copy link
Contributor

@aman4433 aman4433 left a comment

Choose a reason for hiding this comment

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

/lgtm
The timeline looks solid.

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Nov 25, 2025
@k8s-ci-robot
Copy link
Contributor

k8s-ci-robot commented Nov 25, 2025

LGTM label has been added.

Git tree hash: 0baf156677a3828c845607cfdae6ef99a44cfef3

wendy-ha18
wendy-ha18 reviewed Nov 25, 2025
View reviewed changes
docs/release/releases/release-1.13.md
| 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 |
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.

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.

docs/release/releases/release-1.13.md
| 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 |
| v1.13.0-rc.1 released | Release Lead | Tuesday 14th April 2026 | week 15 |
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.

Similarly, this could be v1.13.0-rc.x released.

docs/release/releases/release-1.13.md
| 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 •
edited
Loading

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.

docs/release/releases/release-1.13.md
| 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

@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.

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

@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.

Just thought since this release schedule we should use v before release versions for consistency.

docs/release/releases/release-1.13.md
| 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 |
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.

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 •
edited
Loading

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.

@sbueringer
Copy link
Member

sbueringer commented Nov 25, 2025 •
edited
Loading

/ok-to-test

Thx!

Looks fine in general from my side. I'll defer to @fabriziopandini for a fine-granular review

@k8s-ci-robot k8s-ci-robot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Nov 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@mboersma mboersma Awaiting requested review from mboersma

2 more reviewers

@aman4433 aman4433 aman4433 left review comments

@wendy-ha18 wendy-ha18 wendy-ha18 left review comments

Reviewers whose approvals may not affect merge requirements

Assignees

@aman4433 aman4433

Labels

area/documentation Issues or PRs related to documentation cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@pratik-mahalle @k8s-ci-robot @sbueringer @aman4433 @wendy-ha18