馃摉 Add Cluster API release-1.7 timeline document #9635
Conversation
k8s-ci-robot
added
area/release
k8s-ci-robot
added
cncf-cla: yes
Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>
furkatgofurov7
force-pushed
the
release-1-7-team
branch
from
3a2a0af
to
73a971d
Compare
|
cc @kubernetes-sigs/cluster-api-maintainers FYI |
Done. |
| | *v1.5.x & v1.6.x released* | Release Lead | Tuesday 5th March 2024 | week 14 | | ||
| | v1.7.0-beta.x released | Release Lead | Tuesday 12th March 2024 | week 15 | | ||
| | KubeCon idle week | - | 19th - 22nd March 2024 | week 16 | | ||
| | release-1.7 branch created (**Begin [Code Freeze]**) | Release Lead | Tuesday 26th March 2024 | week 17 | |
There was a problem hiding this comment.
I'm a bit concerned with the code freeze date falling right after kubecon, where maintainers/reviewers will come back after a week away to an inbox full of notifications and there will a lot of last minute PRs that want to get in before code freeze... Not sure if there is another way
There was a problem hiding this comment.
We're doing something similar for this current release with Kubecon NA so we can see how that works out I guess?
There was a problem hiding this comment.
@CecileRobertMichon that is right, it is the same for the current release cycle and this was kind of discussed when adding v1.6 timeline doc: #8901 (comment)
There was a problem hiding this comment.
I think my point is that if this current release cycle doesn't work out well with the code freeze right after kubecon we should consider amending the timeline for 1.7, but we won't know until after we do the code freeze for 1.6.
There was a problem hiding this comment.
As discussed in today's (1/11/23) office hours and pointed out by @CecileRobertMichon, we will see how it works out with the current release cycle and decide based on that for the 1.7 release.
There was a problem hiding this comment.
Just wanted to add that there's also the easter weekend ~ from 29 March - 1 April
There was a problem hiding this comment.
But looks like we already have a 19 weeks cycle, we probably shouldn't extend this further otherwise the other two release cycles will become even shorter in 2024
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. Git tree hash: 60707e07c1b15fb905c0c7fd7ad739b7466c0d59
|
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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
|
/hold let's leave this open until EOD? |
k8s-ci-robot
added
the
do-not-merge/hold
|
/hold cancel |
k8s-ci-robot
removed
the
do-not-merge/hold
What this PR does / why we need it:
This PR adds release-1.7 cycle schedule document with preliminary dates taking into account Kubecon Europe 2024 between March 19-22, 2024 on week 16th in the schedule.
Part of: #9094
/area release
/kind documentation