Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create 1.33 release directory #2706

Open
wants to merge 10 commits into
base: master
Choose a base branch
from
+120 −0
Open

Create 1.33 release directory #2706

Show file tree
Hide file tree
Changes from 1 commit
Commits
Show all changes
10 commits
Select commit Hold shift + click to select a range
3ab1e96
1.33 release directory
npolshakova Dec 23, 2024
ec11d8c
add release lead shadows
npolshakova Dec 30, 2024
af19a15
update OWNERS_ALIASES
npolshakova Jan 3, 2025
6448191
add lead shadows
npolshakova Jan 9, 2025
70f1e66
feedback
npolshakova Jan 13, 2025
b00ed62
add apac start date
npolshakova Jan 13, 2025
5462dd4
signal feedback
npolshakova Jan 13, 2025
a2b07bb
move code freeze
npolshakova Jan 16, 2025
86947d8
fix dates
npolshakova Jan 16, 2025
c6fb0f3
move docs freeze to week 13
npolshakova Jan 17, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 11 additions & 0 deletions releases/release-1.33/OWNERS
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,11 @@
# See the OWNERS docs at https://go.k8s.io/owners

approvers:
- npolshakova # 1.33 Release Team Lead
- neoaggelos # 1.33 Emeritus Advisor

reviewers:
- rytswd # 1.33 Communications Lead
- rayandas # 1.33 Docs Lead
- dipesh-rawat # 1.33 Enhancements Lead
- wendy-ha18 # 1.33 Release Signal Lead
88 changes: 88 additions & 0 deletions releases/release-1.33/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,88 @@
---
title: "Kubernetes 1.33 Release Information"
weight: 98
slug: "release"
aliases: [ "/release" ]
description: |
Information regarding the current release cycle including important dates,
Release Team contact information, tracking spreadsheets and more!
---

# Kubernetes 1.33

#### Links

* [This document](https://git.k8s.io/sig-release/releases/release-1.33/README.md)
* [Release Team](https://github.com/kubernetes/sig-release/blob/master/releases/release-1.33/release-team.md)
* [Meeting Minutes](https://bit.ly/k8s133-releasemtg) (members of [release-team@] receive meeting invites)
* [v1.33 Release Calendar](https://bit.ly/k8s-release-cal)
* Contact: [#sig-release](https://kubernetes.slack.com/archives/C2C40FMNF) on slack, [release-team](mailto://[email protected]) on e-mail
* [Internal Contact Info](https://bit.ly/k8s133-contacts) (accessible only to members of [release-team@])

#### Tracking docs

* [Enhancements Tracking Board](https://bit.ly/k8s133-enhancements)
* [Feature blog Tracking Board](https://bit.ly/k8s133-feature-blogs)
* [Bug Triage Tracking Board](https://bit.ly/k8s133-bugtriage)
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
* [CI Signal Project Board & Issue Tracking](https://bit.ly/k8s133-cisignal)
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
* [Retrospective Document](https://bit.ly/k8s133-retro)
* [kubernetes/sig-release v1.33 milestone](https://github.com/kubernetes/kubernetes/milestone/66)

#### Guides

* [Targeting Issues and PRs to This Milestone](https://git.k8s.io/community/contributors/devel/sig-release/release.md)
* [Triaging and Escalating Test Failures](https://git.k8s.io/community/contributors/devel/sig-testing/testing.md#troubleshooting-a-failure)

## Summary

The 1.33 release cycle is as follows:

- **Monday 13th January 2025**: Week 1 — Release cycle begins
- **Thursday 6th February 2025**: Week 4 — [Production Readiness Freeze](https://groups.google.com/g/kubernetes-sig-architecture/c/a6_y81N49aQ)
- **02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025**: Week 5 — [Enhancements Freeze](../release_phases.md#enhancements-freeze)
- **02:00 UTC Friday 7th March 2025 / 19:00 PDT Thursday 6th March 2025**: Week 9 — [Code Freeze](../release_phases.md#code-freeze) and [Test Freeze](../release_phases.md#test-freeze)
- **Tuesday 25th March 2025**: Week 12 — [Docs Freeze](../release_phases.md#docs-freeze)
- **Tuesday 1st - Friday 4th April 2025**: Week 13 - [KubeCon EU](https://events.linuxfoundation.org/kubecon-cloudnativecon-europe/)
- **Wednesday 16th April 2025**: Week 15 — Kubernetes v1.33.0 released

## Timeline

| **What** | **Who** | **When** | **Week** | **CI Signal** |
|----------------------------------------------------------------------------------------|-------------------------------|-------------------------------------------------------------------------------|----------|--------------------------------------------------------|
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Start of Release Cycle | Lead | Monday 13th January 2025 | week 1 | [master-blocking] |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Start Enhancements Tracking | Enhancements Lead | Monday 13th January 2025 | week 1 | |
| Schedule finalized | Lead | Friday 17th January 2025 | week 1 | |
| Team finalized | Lead | Friday 17th January 2025 | week 1 | |
| Start Release Notes Draft | Release Notes Lead | Tuesday 28th January 2025 | week 3 | |
| 1.33.0-alpha.1 released | Branch Manager | Tuesday 4th February 2025 | week 4 | |
| Begin Friday APAC-friendly meetings | Lead | Wednesday 5th February 2025 | week 4 | |
| **Production Readiness Freeze** | Enhancements Lead | Thursday 6th February 2025 | week 4 | |
| **Begin [Enhancements Freeze]** | Enhancements Lead | 02:00 UTC Friday 14th February 2025 / 19:00 PDT Thursday 13th February 2025 | week 5 | [master-blocking], [master-informing] |
| 1.33.0-alpha.2 released | Branch Manager | Tuesday 18th February 2025 | week 6 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Docs deadline — Open placeholder PRs | Docs Lead | Thursday 20th February 2025 | week 7 | |
| Call for [Exceptions][Exception] | Lead | Monday 24th February 2025 | week 8 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Brace Yourself, Code Freeze is Coming | Comms / Release Signal | Monday 24th February 2025 | week 8 | |
| 1.33.0-alpha.3 released | Branch Manager | Tuesday 25th February 2025 | week 8 | |
| **Begin Feature blog freeze** | Comms Lead | 02:00 UTC Wednesday 26th February 2025 / 19:00 PDT Tuesday 25th February 2025 | week 8 | |
| Deprecations and Removals blog published | Comms | Monday 3th March 2025 | week 9 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| 1.33.0-beta.0 released | Branch Manager | Tuesday 4th March 2025 | week 9 | |
| **Begin [Code Freeze] and [Test Freeze]** | Branch Manager | 02:00 UTC Friday 7th March 2025 / 19:00 PDT Thursday 6th March 2025 | week 9 | |
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks at least 1 week too early. It gives us only 3 weeks for code/test. We need at least 4 weeks, which is what we had in 1.32 and that was actually the shortest code+test we had in the last 12 releases...

See https://docs.google.com/spreadsheets/d/1r7nv5qeSPbU2OieEht6U1it5m4QeS3Iv7a83ujbs7kU/edit?resourcekey=0-vc4oKe2uijpmpoeyjgRfEQ&gid=0#gid=0

@liggitt @thockin @deads2k @soltysh @wojtek-t

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IMO it should be 3/20.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree that it feels very rushed - we have a 3 month cycle and 1/4 of it is development.

That said...

This timeline indicates that the cycle begins Jan 13. But really, it began the moment the tree unfroze. So we have (had) a lot more than just 3 weeks for dev. But the holidays ate all of December, so in PRACTICE, not really.

I don't know how to break the cycle. Every cycle it feels like it gets shorter and less dev-time, then we all argue about it and then we extend it. Can we make it policy to have no less than 4 for dev?

During the March 6-25 window, why can't we continue to allow development, perhaps with the bar higher, but not as high as the final stabilization?

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we make it policy to have no less than 4 for dev?

Definitely agree wrt making a strict policy for 4 dev weeks after the enhancement freeze.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

at least 4 weeks...

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree- I think Week 10 code freeze will give people more time. @katcosgrove would this work with the docs deadlines?

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I am fine with pushing code freeze to week 10. Week 11 is too close to Docs Freeze, considering SIGs already struggle to meet documentation deadlines. I am unwilling to increase pressure on Release Docs and SIG Docs by shortening that timeline even further.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok, so that is the Thursday of Week 10, which starts on 3/24 based on @soltysh's calculations? In other words, 3/27?

Or did you mean 3/20 @katcosgrove ? It seems the math was wrong at some point?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I meant week 10, 3/20. I think the dates and week mappings are fixed here now: https://github.com/kubernetes/sig-release/blob/86947d89fc9958baecf88c66c2336fb3f51b4ab7/releases/release-1.33/README.md

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Also updated docs freeze back to week 13: c6fb0f3 @katcosgrove @chanieljdan @rayandas let me know what you think of the deadlines for the last couple weeks!

| **Preparing for Feature blogs review — Initiating outreach** | Comms | Monday 10th March 2025 | week 10 | |
| **Begin [Burndown]** (Monday, Wednesday, and Friday meetings) | Lead | Monday 17th March 2025 | week 11 | |
| Docs deadline — PRs ready for review | Docs Lead | Tuesday 18th March 2025 | week 11 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Release Highlights deadline | Comms | Tuesday 18th March 2025 | week 11 | |
| Start final draft of Release Notes | Release Notes Lead | Tuesday 18th March 2025 | week 11 | |
| Release blog ready to review | Comms / Docs | 02:00 UTC Friday 21st March 2025 / 19:00 PDT Thursday 20th March 2025 | week 11 | |
| Feature blogs ready to review | Enhancement Owner / SIG Leads | Monday 24th March 2025 | week 12 | |
| Burndown Meetings daily (Tuesday & Thursday over Slack) | Lead | Monday 24th March 2025 | week 12 | |
| release-1.33 branch created | Branch Manager | Tuesday 25th March 2025 | week 12 | |
| release-1.33 jobs created | Branch Manager | Tuesday 25th March 2025 | week 12 | |
| 1.33.0-rc.0 released | Branch Manager | Tuesday 25th March 2025 | week 12 | [1.33-blocking], [master-blocking], [master-informing] |
| **Docs Freeze** | Docs Lead | Tuesday 25th March 2025 | week 12 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| **KubeCon EU** | | Tuesday 1st - Friday 4th April 2025 | week 13 | |
| Release Highlights complete | Release Notes Lead | Tuesday 8th April 2025 | week 14 | |
| 1.33.0-rc.1 released | Branch Manager | Tuesday 8th April 2025 | week 14 | |
| Release Notes complete — reviewed & merged to https://github.com/kubernetes/kubernetes | Release Notes Lead | Wednesday 16th April 2025 | week 15 | |
| **v1.33.0 released** | Branch Manager | Wednesday 16th April 2025 | week 15 | [1.33-blocking], [master-blocking], [master-informing] |
| Release blog published | Comms | Wednesday 16th April 2025 | week 15 | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| [Thaw] | Branch Manager | Wednesday 16th April 2025 | week 15 | |
15 changes: 15 additions & 0 deletions releases/release-1.33/release-team.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,15 @@
# Kubernetes 1.33 Release Team

| **Team/Role** | **Lead Name** (**GitHub / Slack ID**) | **Shadow Name(s) (GitHub / Slack ID)** |
|-------------------|----------------------------------------------------------------------------------------------|----------------------------------------|
| Release Team Lead | Nina Polshakova ([@npolshakova](https://github.com/npolshakova) / Slack: `@Nina Polshakova`) | |
npolshakova marked this conversation as resolved.
Show resolved Hide resolved
| Emeritus Adviser | Angelos Kolaitis ([@neoaggelos](https://github.com/neoaggelos) / Slack: `@Angelos Kolaitis`) | N/A |
| Enhancements | Dipesh Rawat ([@dipesh-rawat](https://github.com/dipesh-rawat) / Slack: `@Dipesh`) | |
| Communications | Ryota Sawada ([@rytswd](https://github.com/rytswd) / Slack: `@Ryota`) | |
| Release Signal | Wendy Ha ([@wendy-ha18](https://github.com/wendy-ha18) / Slack `@Wendy Ha`) | |
| Docs | Rayan Das ([@rayandas](https://github.com/rayandas) / Slack: `@rayandas`) | |
| Branch Manager | | |

Review the [Release Managers page](https://github.com/kubernetes/website/blob/main/content/en/releases/release-managers.md) for up-to-date contact information on Release Engineering personnel.

The schedule for all patch releases can be found at [Patch Releases page](https://github.com/kubernetes/website/blob/main/content/en/releases/patch-releases.md). It will be updated to include 1.33, once the 1.33 release cycle concludes.