Open drewhagen opened 1 week ago
@drewhagen: The label(s) /label sig-release
cannot be applied. These labels are supported: api-review, tide/merge-method-merge, tide/merge-method-rebase, tide/merge-method-squash, team/katacoda, refactor
. Is this label configured under labels -> additional_labels
or labels -> restricted_labels
in plugin.yaml
?
/sig release
/assign
Nice job on creating this checklist.
Mid-Release Cycle (~week 6-9, Oct 12th - Nov 7th) 📆⚠️ Code Freeze is 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024
Monitor the master-blocking, master-informing, release-x.y-blocking and release-x.y-informing dashboards on a daily basis.
This is wrongly documented in the handbook (which I'll update alongside creating a one-pager).
The release-x.y boards are set alongside the rc-0
cut. Usually, it takes 2-3 days, sometimes even a week, to get those boards set up and stabilized.
Often, some job misconfiguration/some other bugs can be patched by the Release Signal Lead. So I'll include this and monitor/help with setting up release-x.y boards after rc-0
cut to the list.
I've assigned myself to create a one-pager.
@Vyom-Yadav Are there any GitHub Actions or other automated code that I should be aware of?
I'm curious to gain more knowledge to cover this if needed:
Updating/Extending scripts/actions that populate the Bug Triage and CI Signal project board with relevant issues/PRs.
⚠️ The following is a work in progress and somewhat experimental, to create an issue to track my work similar to the Release Lead. Follows the Release Signal Handbook that details the team's responsibilities.
Onboarding
milestone:v1.32
Status
issue toPending inclusion
for all open issues and PRs targeting the current release cycleEarly Release (~week 0-5, Sept. 3rd - Oct. 11th)**
📆 Release cycle begins Monday Sept 9th. ⚠️ Drew will be OOO from Sept 11th - 14th. Vyom agrees to be main coordinator of the test grid during this time.
Delegate No/Go Signal for Alpha Release Cuts
Following guidance in the handbook and assignments in the spreadsheet, see that the assigned member of Release Signal gives the Go/No Go signal to Branch Management.
Mid-Release Cycle (~week 6-9, Oct 12th - Nov 7th)
📆⚠️ Code Freeze is 02:00 UTC Friday 8th November 2024 / 19:00 PDT Thursday 7th November 2024
Delegate No/Go Signal for Beta Release Cut
Following guidance in the handbook and assignments in the spreadsheet, see that the assigned member of Release Signal gives the Go/No Go signal to Branch Management.
Preparing for Code Freeze (before Thursday Nov 7th)
is:pr is:open milestone:v1.28 label:approved label:lgtm -label:do-not-merge/hold
is:pr is:open milestone:v1.28 label:approved label:lgtm label:do-not-merge/hold
is:pr is:open milestone:v1.28 -label:approved label:lgtm
is:pr is:open milestone:v1.28 label:approved -label:lgtm
Day of Code Freeze (on Thursday Nov 7th)
Day After Code Freeze (Friday Nov 8th)
/milestone v1.33
if they are planned for the next cycle or had recent activity./milestone clear
command.📆 KubeCon NA and Contrib Summit (Monday Nov 11 - Friday Nov 15th)
One Week After Code Freeze (Thursday Nov 14th)
Week 1 of Code Freeze (Thursday Nov 7th) until Code Thaw (Wednesday Dec 11th)
/milestone v1.xx
./milestone clear
.Delegate No/Go Signal for Release Candidate Cuts
Following guidance in the handbook and assignments in the spreadsheet, see that the assigned member of Release Signal gives the Go/No Go signal to Branch Management.
Code Thaw (One Week Before Release Target Date?? December 3rd?)
Delegate No/Go Signal for Release Cut
Following guidance in the handbook, see that a member of Release Signal signals to Branch Management.