[RFC] Projecting next cycle's release schedule

43 views

Skip to first unread message

unread,

May 11, 2021, 5:26:29 PM5/11/21

to kuberne...@googlegroups.com, le...@kubernetes.io, sig-rele...@kubernetes.io

Kubernetes Community --

As part of today's SIG leads meeting (non-recorded), we discussed the following thread requesting deadline changes in the v1.22 release cycle: https://groups.google.com/g/kubernetes-sig-release/c/8mn7HijIxlA

While we decided amongst @kubernetes/sig-release-leads and @kubernetes/release-team-leads that we will not be further altering the Enhancements Freeze date for v1.22, the leads discussion did bring us to an actionable request:

Can SIG Release endeavor to provide dates for the following release cycle ahead of time?

I think it's something we can definitely strive to do!

Here's an idea of workflow:

SIG Release leads set a framework for devising the schedule: https://github.com/kubernetes/enhancements/tree/master/keps/sig-release/2572-release-cadence#schedule-policy
The current cycle's Release Team Lead shadows (+/- RT lead) and Emeritus Adviser present a notional schedule to SIG Release leads
If approved, the notional schedule is then presented to the current Release Team for further feedback
One of the schedule author's (RT Lead shadows or EA) open a schedule PR by foo date (which deadline should this align to?)
Open wider community comment period to end by bar date (set lazy consensus; maybe Code Freeze?)
Resolve feedback
Merge
Announce

---

Stephen Augustus (he/him)

Head of Open Source

Emerging Tech & Incubation

My working hours may not be your working hours.
Please do not feel obligated to reply outside of your normal work schedule.