Replies: 7 comments 2 replies
-
cc @kubernetes/release-team-leads @reylejano @Priyankasaggu11929 |
Beta Was this translation helpful? Give feedback.
-
To me it seems feasible to move the freeze out 1 additional week given that 1.21 was week 5 |
Beta Was this translation helpful? Give feedback.
-
I am in favor of moving enhancement freeze to week 5 due to
Plus, people don't need to wait until release cycle begin to start the enhancement submission/review for current release. The enhancement submission/review could happen earlier if they feel it might require more time. |
Beta Was this translation helpful? Give feedback.
-
+1 to everything commented above. I am in huge favor of pushing the enhancement freeze to week 5. We (the Enhancements Team) are already aware of SIGs with KEPs in flight but not yet tracked in the sheet. And we're already in the last week of the 1.25 Enhancements Freeze. By adding (at least) one week, both KEP owners and the enhancements team would be able to track more KEPs on time. |
Beta Was this translation helpful? Give feedback.
-
I'm personally happy to give 1 more week to work on enhancements. I'm wondering if this solves the real problem or just reduces the pain of the symptoms. For example, more ad-hoc enhancements means also more required reviews from sides where we're already low on bandwidth, for example PRR and SIG Architecture. I think it would be better if more enhancements gets reviewed and merged during the current cycle, so that they can fill a backlog of items which can be added to the next cycle right before it starts. |
Beta Was this translation helpful? Give feedback.
-
I agree with @salaxander , @cici37 , @Priyankasaggu11929 , and @saschagrunert comments to push Enhancements Freeze by 1 week |
Beta Was this translation helpful? Give feedback.
-
Thank you so much to everyone for considering extending the Enhancements Collection period! ❤️ |
Beta Was this translation helpful? Give feedback.
-
@thockin Raised a concern of KEP deadline being too quick on twitter and slack.
Quoted from slack discussion:
Here is the discussion on when is the optimal start of Enhancements Freeze in 1.25 release cycle and beyond.
For reference:
In Kubernetes 1.22, Enhancements Freeze was moved 2 weeks earlier to week 3 of the release cycle.
Starting in Kubernetes 1.23, Enhancements Freeze is coupled with the requirement of having a Production Readiness Review questionnaire to be filled out 1 week before the start of Enhancements Freeze (ref: communication email).
Kubernetes 1.20, Enhancements Freeze started on week 4 of the release cycle
Kubernetes 1.21, Enhancements Freeze started on week 5 of the release cycle
Kubernetes 1.22, Enhancements Freeze started on week 3 of the release cycle
Kubernetes 1.23, Enhancements Freeze started on week 3 of the release cycle
Kubernetes 1.24, Enhancements Freeze started on week 4 of the release cycle
The current Kubernetes 1.25 release cycle, Enhancements Freeze is scheduled to start on week 4 of the release cycle
The metrics(Thanks @reylejano for making the initial metrics here):
The previous discussion on the enhancement freeze date happening here.
Beta Was this translation helpful? Give feedback.
All reactions