Create v1.37 release directory and schedule#3016
Conversation
k8s-ci-robot
added
the
kind/documentation
k8s-ci-robot
added
the
area/release-team
k8s-ci-robot
added
sig/release
|
/cc katcosgrove fsmunoz |
k8s-ci-robot
added
the
lgtm
|
/lgtm |
| The v1.37 release cycle is proposed as follows: | ||
|
|
||
| - **Monday 18th May 2026**: Week 1 — Release cycle begins | ||
| - **Thursday 11th June 2026 (AoE) / Friday 12th June 2026, 12:00 UTC**: Week 4 — [Production Readiness Freeze][Production Readiness Freeze] |
There was a problem hiding this comment.
v1.36 moved most deadlines (PRR, Enhancements, Code/Test Freeze) from Thursday AoE to Wednesday AoE based on a retro item, so the release team has Thursday/Friday to handle exceptions before the weekend. This PR uses Thursday AoE for PRR Freeze, Enhancements Freeze, and Code/Test Freeze. Was that intentional, or was this based on an older template?
There was a problem hiding this comment.
yeah i think these freezes should be shifted a day earlier. 1.36 used Wed AoE (Thurs noon UTC)
There was a problem hiding this comment.
Thanks for pointing this out. I remembered this incorrectly that we used Wednesday AoE in the spring and winter releases to account for KubeCon EU/NA and allow time for exception handling.
There was a problem hiding this comment.
I’ve adjusted PRR Freeze and Enhancements Freeze to Tuesday AoE instead of Wednesday AoE to account for KubeCon India and the Juneteenth holiday, without shortening the development cycle by moving the deadlines a full week later.
addressed as part of commit 95c504d
|
|
||
| - **Monday 18th May 2026**: Week 1 — Release cycle begins | ||
| - **Thursday 11th June 2026 (AoE) / Friday 12th June 2026, 12:00 UTC**: Week 4 — [Production Readiness Freeze][Production Readiness Freeze] | ||
| - **Thursday 18th June 2026 (AoE) / Friday 19th June 2026, 12:00 UTC**: Week 5 — [Enhancements Freeze][Enhancements Freeze] |
There was a problem hiding this comment.
KubeCon India 2026 is June 18-19 in Mumbai, which overlaps directly with this deadline. The UTC cutoff (Friday June 19, 12:00 UTC) also falls on Juneteenth (US federal holiday). In v1.34, the Enhancement Freeze was shifted by a day specifically because of Juneteenth. Worth considering whether to adjust this date.
There was a problem hiding this comment.
I’ve adjusted PRR Freeze and Enhancements Freeze to Tuesday AoE instead of Wednesday AoE to account for KubeCon India and the Juneteenth holiday, without shortening the development cycle by moving the deadlines a full week later.
addressed as part of commit 95c504d
|
|
||
| ## <a id="contacts"></a> Contacts | ||
|
|
||
| _To be updated_ No newline at end of file |
There was a problem hiding this comment.
Missing trailing newline. Also, the README references rel.k8s.io/v137/feature-blogs in the Tracking docs section, but there is no feature-blogs anchor in this file. Consider adding a placeholder section for it (v1.36 had the same gap).
There was a problem hiding this comment.
re: feature-blogs, searching past discussions reminded me that we don't always reliably populate this link. In 1.33 and 1.35 it pointed to the "Comms - Feature Blogs" view of the tracking board, but 1.34 and 1.36 didn't have such a shortlink (cc @dipesh-rawat in case you want to add it for 1.37)
There was a problem hiding this comment.
Looking at the Tracking docs section, it duplicates the release links we maintain through links.md since the transition to rel.k8s.io. I replaced that section with a single link to links.md.
There was a problem hiding this comment.
Also, dropped the separate feature-blogs link, since that just points to a view in the Enhancements board, which is already linked from links.md.
addressed as part of commit 95c504d
|
/hold Just to prevent an accidental merge before sufficient discussion and input. :) |
k8s-ci-robot
added
the
do-not-merge/hold
k8s-ci-robot
removed
the
lgtm
dipesh-rawat
force-pushed
the
create-v1.37-release-directory
branch
from
ecf6a0e to
95c504d
Compare
k8s-ci-robot
added
the
lgtm
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: dipesh-rawat, fsmunoz, saschagrunert The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
6 participants
What type of PR is this:
/kind documentation
What this PR does / why we need it:
Creates the v1.37 release directory with the initial release docs as per #3015.
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
This is part of the initial setup for the v1.37 release cycle.