🌱 Postpone v1.11 code freeze by one week #12498
Conversation
k8s-ci-robot
added
do-not-merge/work-in-progress
k8s-ci-robot
added
the
size/S
|
@amitami2: changing LGTM is restricted to collaborators In response to this:
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. |
|
/lgtm |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 652a5547fca6c82416407542e7cfaa39da74b206
|
sbueringer
changed the title
k8s-ci-robot
removed
the
do-not-merge/work-in-progress
|
Removed WIP from the PR |
| @@ -21,13 +21,13 @@ The following table shows the preliminary dates for the `v1.11` release cycle. | |||
| | Communicate beta to providers | Comms Mgr | Tuesday 15th July 2025 | week 12 | | |||
| | Communicate upcoming code freeze to the community | Comms Mgr | Tuesday 15th July 2025 | week 12 | | |||
| | v1.11.0-beta.x released | Release Lead | Tuesday 22nd July 2025 | week 13 | | |||
There was a problem hiding this comment.
Can we add another beta here in between. Just so we still have weekly releases from beta.0 until GA
There was a problem hiding this comment.
@kubernetes-sigs/cluster-api-release-team Is that okay for you?
There was a problem hiding this comment.
I think that should be fine. 👍🏻
There was a problem hiding this comment.
Added onee more beta, PTAL
k8s-ci-robot
removed
the
lgtm
fabriziopandini
added
the
tide/merge-method-squash
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sbueringer 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 |
k8s-ci-robot
added
the
approved
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 5542b3bbd1c3453f2fe2d8b59e1f5e948b252448
|
What this PR does / why we need it:
... pending office hours discussion
This PR moves code freeze + following deadlines by one week in order to give a little bit more room to complete the v1beta2 work an most specifically #12497
It also fit nicely with the fact that K8s release this year is one week later than usual.