search

kubernetes / sig-release

Repo for SIG release
Apache License 2.0
521 stars 379 forks source link

Update release signal's internal assignments process #2509

Closed Vyom-Yadav closed 1 month ago

Vyom-Yadav commented 1 month ago

What type of PR is this:

/kind documentation

What this PR does / why we need it:

As discussed in the v1.30 release retro., the release signal team needs to move away from the on-call scenario to get more than 1 shadow involved in the observing testgrid dashboard and other tasks at a time. This change allows a shadow to assign tasks to other shadows (which is also good for training the shadow to be a lead) and allows for the involvement of more than 1 shadow at any time.

Of course, this approach only works if the main coordinator (new internal shadow role) assigns the tasks to the other shadows. It is the duty of the release signal lead to ensure that this happens and that the maximum stuff is assignment-based rather than passing responsibilities from one on-call to the next one.

Which issue(s) this PR fixes:

None

Special notes for your reviewer:

/cc @katcosgrove @gracenng @Priyankasaggu11929 @pacoxu

k8s-ci-robot commented 1 month ago

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: pacoxu, Vyom-Yadav

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: - ~~[release-team/role-handbooks/release-signal/OWNERS](https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/release-signal/OWNERS)~~ [Vyom-Yadav,pacoxu] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment
Vyom-Yadav commented 1 month ago

@katcosgrove @gracenng @Priyankasaggu11929 If you think some changes need to be made, please add a review comment, and I'll incorporate that in a separate PR.