Closed npolshakova closed 3 weeks ago
Hey @npolshakova, great job on getting this done! Overall it looks good, and I've added a few comments. Let me know what you think!
/lgtm
/assign @harshanarayana
/lgtm /approve
/hold
@npolshakova, please feel free to remove hold whenever PR is ready to merge. :slightly_smiling_face:
Thanks for the updates! :pray:
/unhold
/approve /lgtm
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: npolshakova, Priyankasaggu11929, rashansmith, saschagrunert
The full list of commands accepted by this bot can be found here.
The pull request process is described here
What type of PR is this:
/kind documentation
What this PR does / why we need it:
This adds an example for defining release notes draft PR merge deadline. Currently, the timeline only defines when a branch is created, and we assume to get the PR done sometime before the next branch is made. This would be only internally enforced and used to give status updates.
Previously Release Notes Leads have created similar schedules for assigning shadows to "own" a specific release: https://docs.google.com/spreadsheets/d/1xNNWdh-hFTVgg-zebp0-DdV-gCnx5l3uUv3RikjAzBg/edit?usp=sharing
The 1.30 end of release retro suggested adding a release notes draft PR merge deadline that would be tied to status reports during release team update meetings.
Which issue(s) this PR fixes:
https://github.com/kubernetes/sig-release/issues/2498