[NOTICE] Kubernetes Release Schedule Update
Kat Cosgrove
Kubernetes Contributors and Maintainers,
Over time, the Release Team has watched the number of Code Freeze exception requests per cycle slowly increase. This cycle was the largest number of exception requests we have fielded so far, and an increasingly common explanation for needing an exception is the shortage of reviewer and approver time near Code Freeze. The Release Team is unable to materialize more reviewers and approvers for you (our apologies), but we can give you more time.
Beginning with v1.38, we are going to attempt to create more space in the release cycle, hopefully reducing the number of exception requests necessary and increasing the number of KEPs that make it. Instead of a two-week gap between cycles that we use to gather applicants for release team shadows, we will open the shadow application and begin team selection in the last two weeks of the current cycle.
This will allow us to officially start the next cycle as early as the Monday after a release and give us (roughly) two more weeks in a cycle, which we will put between Enhancements Freeze and Code Freeze. We believe that this additional breathing room will be more effective and less disruptive than the compressing schedules to increase the number of release cycles per year.
For us, this means beginning our end-of-cycle work a little early and reducing the period of time we usually have to make updates to the role handbooks. For you, this means significantly more time to get PRs ready, reviewed, and merged. We hope that this takes some pressure off all of you. :)
XOXO,
Kat Cosgrove and Frederico Muñoz
Release Team Subproject
Benjamin Elder
--
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 visit https://groups.google.com/d/msgid/kubernetes-sig-release/CABHW_BfnpYEgoOaGQ%3DSagZraVpE_sbuHJ-D%3D%3DjM6tWia3rE7%3DA%40mail.gmail.com.