Updating documentation: Post 1.29 Enhancements Role Handbook Updates #2375
Description
Umbrella issue to improve the Enhancements Role Handbook to clarify some things that have been points of confusion in this (and previous) releases.
- Add a reference to clarify what “PRR Freeze” means to handbook
- Link this email from PRR team in our Enhancements handbook (maybe in the outreach templates)
- PRR freeze has always been a soft deadline due to a limited PRR reviewers handling multiple KEPs, making it tough to finish all reviews by the deadline
- notify people in #prod-readiness about KEPs waiting for PRR reviews since the enhancement freeze is coming up next week with project board filter with KEPs missing PRR assignee
- Clarified PRR freeze and exceptions.yaml in enhancements handbook #2518 - Add section to clarify test freeze in the enhancements handbook
- What is the test freeze
- Clarify code freeze checks - Add clarification for KEPs with only bug fixes going into release are fine to mark as
tracked for code freezefor the purposes of enhancements tracking. - Add instructions to help Comms team compile the major themes to handbook
- Add guidelines for creating new Project Board from template in Github
- If we need additional automation that’s more declarative, Mark started this PR a while back that we can revisit: WIP - Script to create new project baords marosset/sig-release#1 - Add instructions for enabling/disabling test-infra job that does enhancement collection based on lead-opted-in label
- Enable periodic enhancements sync for v1.29 test-infra#30528
- Disable enhancements project board job for 1.29 Enhancement Freeze test-infra#30965 - Clarify code freeze cut offs in handbook (PRs must at least be approved by SIG reviewers and in the merge queue)
- Add example for exceptions.yaml file in the handbook