Skip to content

📖 Add Cluster API release-1.11 timeline document #12122

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
Merged
merged 1 commit into from
Apr 30, 2025
Merged

📖 Add Cluster API release-1.11 timeline document #12122

merged 1 commit into from
Apr 30, 2025

Conversation

mboersma
Copy link
Contributor

What this PR does / why we need it:

This PR adds the release-1.11 cycle schedule document with preliminary dates and release team members.

Part of: #11656

/area release
/kind documentation

@k8s-ci-robot k8s-ci-robot added area/release Issues or PRs related to releasing kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Apr 23, 2025
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Apr 23, 2025
@mboersma
Copy link
Contributor Author

/cc @cprivitere @fabriziopandini

@cprivitere
Copy link
Member

/lgtm

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

LGTM label has been added.

Git tree hash: 5f9f4dfcec3ff2b6aefdfab81f36ee83b6085bcd

@cprivitere
Copy link
Member

/approve

@cprivitere
Copy link
Member

/assign @mboersma

@cprivitere cprivitere removed their assignment Apr 23, 2025
fabriziopandini
fabriziopandini reviewed Apr 24, 2025
View reviewed changes
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

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

At high level I think that CAPI v1.11 should be a 16 week release starting W18 (next week), end ending on W33 (Aug 12th GA)

Week/Calendar Week/Release Week start day Release activity Patch planning
18 1 Apr 28, 2025 Start + Schedule & team finalized 1.10 extra patch
19 2 May 5, 2025    
20 3 May 12, 2025    
21 4 May 19, 2025   Monthly patch
22 5 May 26, 2025 alpha-0  
23 6 Jun 2, 2025    
24 7 Jun 9, 2025    
25 8 Jun 16, 2025 alpha-1? Monthly patch
26 9 Jun 23, 2025    
27 10 Jun 30, 2025 alpha-2 ?  
28 11 Jul 7, 2025    
29 12 Jul 14, 2025 Beta-0 Monthly patch
30 13 Jul 21, 2025 Beta-1  
31 14 Jul 28, 2025 rc-0 / Code freeze  
32 15 Aug 4, 2025 rc-1  
33 16 Aug 11, 2025 GA Monthly patch

This gives us room for CAPI v1.12 to be a 17 weeks release (W34-W50) + 1 Week buffer and 1 Week of XMAS break.

Also, please note we should consider one alpha for allowing folks to start testing on v1beta2 API as soon as possible

WDYT?

@mboersma
Copy link
Contributor Author

At high level I think that CAPI v1.11 should be a 16 week release starting W18...

That all makes sense to me. I'll redo it based on your feedback. Thanks @fabriziopandini!

@mboersma mboersma force-pushed the release-1.11-team branch from 5cde917 to c7b649c Compare April 24, 2025 22:17
@k8s-ci-robot k8s-ci-robot removed the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 24, 2025
@mboersma
Copy link
Contributor Author

Updated with new dates for the CAPI v1.11 calendar.

fabriziopandini
fabriziopandini reviewed Apr 25, 2025
View reviewed changes
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

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

Last round of nits from my side, but it looks great

@mboersma mboersma force-pushed the release-1.11-team branch from 9c9bd87 to 5c2dc27 Compare April 25, 2025 15:18
@mboersma mboersma force-pushed the release-1.11-team branch from 5c2dc27 to ff3cf63 Compare April 25, 2025 15:19
fabriziopandini
fabriziopandini reviewed Apr 25, 2025
View reviewed changes
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

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

/lgtm

I will approve + merge after @cprivitere lgtm

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

LGTM label has been added.

Git tree hash: fda3febfa5bf213110a9673cb1c6302945e1d73f

cprivitere
cprivitere approved these changes Apr 29, 2025
View reviewed changes
Copy link
Member

@cprivitere cprivitere left a comment

Choose a reason for hiding this comment

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

/lgtm

@cprivitere
Copy link
Member

@fabriziopandini Looks good here.

fabriziopandini
fabriziopandini reviewed Apr 30, 2025
View reviewed changes
Copy link
Member

@fabriziopandini fabriziopandini left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cprivitere, fabriziopandini

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

The pull request process is described 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 the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 30, 2025
@k8s-ci-robot k8s-ci-robot merged commit 0150847 into kubernetes-sigs:main Apr 30, 2025
16 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.11 milestone Apr 30, 2025
@mboersma mboersma deleted the release-1.11-team branch April 30, 2025 18:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@fabriziopandini fabriziopandini fabriziopandini left review comments

@cprivitere cprivitere cprivitere approved these changes

@chandankumar4 chandankumar4 Awaiting requested review from chandankumar4

@wendy-ha18 wendy-ha18 Awaiting requested review from wendy-ha18

Assignees

@mboersma mboersma

@fabriziopandini fabriziopandini

@cprivitere cprivitere

Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release Issues or PRs related to releasing cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Milestone
v1.11
Development

Successfully merging this pull request may close these issues.
4 participants
@mboersma @cprivitere @k8s-ci-robot @fabriziopandini