Request - rename PRR Freeze for 1.34

[johnbelamaric]

Hi SIG Release,

Every cycle the "PRR Freeze" causes confusion. I try to send out emails to clarify (example 1, example 2), but it's only marginally helpful.

What if we renamed it do something without the word "Freeze"? Maybe "PRR Submission Deadline"? To make it clear that it is for submission of the PRR section, not approval of the section?

cc @kubernetes/prod-readiness-reviewers

[BenTheElder]

Agreed, I think it's very different from code freeze or enhancements freeze where we expect review to be done and everything merged.

[soltysh]

This topic was discussed during prod-readiness sync on 4/30 (recording). The prod-readiness team agreed to make the Production Readiness Freeze (1 week prior to Enhancement Freeze) a hard deadline, by which KEP authors are required to open an update PR. Failing to meet that requirement would automatically trigger the exception process.

This topic was brought to sig-release sync on 5/06 during which the sig-release agreed they will try to implement this for 1.34 (best effort), and will enforce it starting 1.35+.

[sreeram-venkitesh]

Adding v1.34 enhancements lead @jenshu to the thread.

CC: @Vyom-Yadav @katcosgrove

[katcosgrove]

Hi folks! Starting this cycle (v1.34) the Enhancement subteam will remind KEP owners of the PRR deadline. However, we will not be checking in on that process, enforcing a hard deadline, or handling an exception process for people who miss the deadline.

Beginning with v1.35, we will take over enforcement of the PRR deadline and the handling of exception requests. I'll tag you when I open relevant PRs to update release team documentation.