Skip to content
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 Cluster API release-1.10 timeline document #11479

Merged
merged 1 commit into from
Dec 16, 2024

Conversation

Sunnatillo
Copy link
Contributor

@Sunnatillo Sunnatillo commented Nov 26, 2024

This PR adds release-1.10 cycle schedule document with preliminary dates taking into account Kubecon Europe 2025 between April 1-4, 2025 on week 16th in the schedule.

Part of: #11092

/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 Nov 26, 2024
@k8s-ci-robot k8s-ci-robot added the size/M Denotes a PR that changes 30-99 lines, ignoring generated files. label Nov 26, 2024
@Sunnatillo
Copy link
Contributor Author

/cc @fabriziopandini @sbueringer


| **What** | **Who** | **When** | **Week** |
|------------------------------------------------------|--------------|-----------------------------|----------|
| Start of Release Cycle | Release Lead | Monday 16th December 2024 | week 1 |
Copy link
Member

Choose a reason for hiding this comment

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

What about moving the start of the release cycle to Jan 6h, I don't think that nothing meaningful will happen during xMas break

Note: This will will shorten the release cycle from 19 to 17 weeks to keep us on track for 3 release also in 2025. Also, we already had a few 17 weeks release cycles, so I think it is ok.

Copy link
Member

Choose a reason for hiding this comment

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

No strong opinion, but may be good to do for the folks that will be part of the release team :-)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I agree with @fabriziopandini.

docs/release/releases/release-1.10.md Outdated Show resolved Hide resolved
docs/release/releases/release-1.10.md Outdated Show resolved Hide resolved
@fabriziopandini
Copy link
Member

cc @chrischdi

@Sunnatillo Sunnatillo force-pushed the add-v1.10-timeline/sunnat branch from ef518c9 to 6b8ad79 Compare December 2, 2024 11:02
@fabriziopandini
Copy link
Member

/lgtm
/approve
/hold for lazy consensus EOW

cc @vincepri @enxebre

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 2, 2024
@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Dec 2, 2024
@k8s-ci-robot
Copy link
Contributor

LGTM label has been added.

Git tree hash: d5c91d586166b3fa502c1e805f2bc413aa0989c2

@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: 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 Dec 2, 2024
@chrischdi
Copy link
Member

/lgtm

@fabriziopandini
Copy link
Member

/hold cancel
Lazy consensus deadline expired

@k8s-ci-robot k8s-ci-robot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Dec 16, 2024
@k8s-ci-robot k8s-ci-robot merged commit c254e63 into kubernetes-sigs:main Dec 16, 2024
17 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.10 milestone Dec 16, 2024
@Sunnatillo Sunnatillo deleted the add-v1.10-timeline/sunnat branch December 17, 2024 07:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
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
Development

Successfully merging this pull request may close these issues.

4 participants