Hi Folks,
Thanks for bringing up this concern. We had a discussion around the enhancements freeze in the Release 1.22 Schedule PR about reducing the duration of freeze to 2 weeks from 4 weeks and solicited public feedback. Since the two week deadline for enhancements freeze requested during public discussions with the community [1][2] coincided with KubeCon, we extended it by a week. With this we ensured we could cater to both the requests made, namely increasing development time and ensuring more time for reviewing, by settling for a compromise of 3 weeks. There were no rejecting/negative comments noted at the time of discussion/final merge of the schedule.
The Release Team understands the difficulty in reviewing PRs during/right after KubeCon week and we have provided an additional five days for this reason. Combined with the Call for Exceptions, we believe that we arrived at an acceptable compromise that would ensure more time for development and for reviewing after KubeCon. However, we are always looking to make the release cycle as smooth and as efficient as possible for everyone in the community and would therefore be adding this topic to the 1.22 retro. If you do have suggestions on how we could communicate/plan this better, we would love to hear your feedback and incorporate them in the coming cycles.
Regards,
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/1c4165e6-5873-4671-ad01-1b006edd3292n%40googlegroups.com.
Hi,
Firstly, apologies for poking this thread again so late.
I wanted to echo Tim’s question again - would the release team be willing to reconsider moving the enhancement freeze deadline by a week? With the deadline just a few days after KubeCon, it puts a lot of pressure on contributors. Also, given that there are contributors across the world and there are countries going through major crises right now (e.g. the covid crisis in India), it would be helpful to be empathetic to the community to offer some breathing space here.
It also looks like moving the enhancement freeze deadline would not have any major detrimental impact.
Thanks,
Nikhita
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CADTKTkR-m4%2BPn-yi5_JsJowZCh35sbaR6%2BV7jszn220%3D3jgCHg%40mail.gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/CAFPyxnK0XgRA373jg2_%2BvfsJTeFYGYZAO7km6d26cpiu5n1fjw%40mail.gmail.com.
Hi All,
Thanks for adding your thoughts and concerns. After discussing internally, the Release Team has decided not to extend the deadline for enhancements freeze. As we mentioned in this email chain, we arrived at this schedule after soliciting comments and feedback. In case you miss the enhancements freeze deadline, we would like you to please follow the exception process to get your enhancements tracked. If you have any questions about the exceptions process, please feel free to reach out to us or in #sig-release.
We are constantly on the lookout for improving the release process for contributors all over the world. If you have suggestions on the schedule (or anything related to the release process) we would love your feedback to help improve future releases.Regards,