"Production Readiness Freeze" is misnamed

[johnbelamaric]

Hi all,

I opened a similar issue in the past (#2733 ) and it was resolved when the release team started enforcing the requirements at PRR freeze time (which is awesome, thank you!). But I still think the name causes confusion. In fact, this isn't just PRR anymore, it's really "KEP Ready for Full Review Deadline" or something like that. For example, your KEP must now be lead opted-in and milestoned by this date as well.

Maybe next cycle we can rename it? People still think it's a deadline for PRR approval, because of the name. If we just named it "KEP Review Readiness Deadline" I think that would be more accurate and cause less confusion.

cc @soltysh @sohankunkerkar

[dipesh-rawat]

Thanks for raising this. I agree the current PRR Freeze wording can be confusing give the deadline covers more than PRR alone: enhancements must be opted in, added to the milestone, and have KEP files ready for review.
My initial suggestion would be Enhancement Review Readiness Deadline. I’ll add this as a v1.37 retro item so we can discuss naming for the next cycle.

cc @katcosgrove @fsmunoz for visibility as Release Team subproject leads.

[soltysh]

Maybe next cycle we can rename it? People still think it's a deadline for PRR approval, because of the name. If we just named it "KEP Review Readiness Deadline" I think that would be more accurate and cause less confusion.

Maybe something like "KEP Submission Deadline" will be most appropriate. It clearly states the submission part, which is what we're shooting for. Alternative, I can think of (with some googling around) is "KEP Review Cutoff".

[fsmunoz]

I took the liberty of adding this to the Retro Action Items board. I agree with the idea, I believe we are overloading the PRR term (and by now we're all so used to it that it has lost most of the connection with the name itself). "KEP Readiness Deadline" or something would work for me, but all suggestions look adequate. Goal would be to discuss this in this next retro and prepare for any change in the v1.38 release (cc @katcosgrove for comments/corrections).