✨ Remaining Important Deadlines for v1.33 Release ✨
1 view
Skip to first unread message
nina polshakova
Mar 28, 2025, 12:37:12 PMMar 28
to d...@kubernetes.io, le...@kubernetes.io, kubernetes-...@googlegroups.com, releas...@kubernetes.io
Hello Kubernetes community!
With KubeCon EU just around the corner, we want to remind you about a couple of key deadlines coming up after the conference as we map out the remaining release milestones:
Feature Blogs
Feature blogs are a great way to spotlight your enhancement and showcase its impact on the community. This is especially encouraged for high-visibility changes as well as deprecations and removals. You can view the current opted-in features on the Comms team’s Github board. If you have opted in, please make sure your blog is ready for review by the Feature Blog Freeze deadline (April 10th).
If you have any questions, please reach out to the comms team in the #release-comms Slack channel!
Best,
Nina Polshakova, on behalf of the v1.33 Release Team.
"...Anyway, what is a fantasy map but a space beyond which There Be Dragons?"
— Terry Pratchett, The Color of Magic
TL;DR: 63 enhancements post-Code/Test Freeze. Please be aware of the docs and blogs deadlines below.
The v1.33 code freeze went smoothly—huge thanks to all the KEP authors and reviewers for making the process seamless. We have 63 tracked enhancements this cycle! You can see all the tracked enhancements on the GitHub project board.
- Docs Freeze — 02:00 UTC Wednesday, 9th April 2025 / 19:00 PDT Tuesday, 8th April 2025: Week 13
- Feature Blog Freeze — 02:00 UTC Friday, 11th April 2025 / 19:00 PDT Thursday, 10th April 2025: Week 13
- v1.33.0-rc.1 released — Tuesday 15th April 2025
- v1.33 Release Target Date — Wednesday 23rd April 2025
Documentations
Unless the KEP changes do not require any updates to the website, please open a PR against the `dev-1.33` branch on `kubernetes/website. ' Instructions to create a placeholder PR are here. All enhancements that are determined to require documentation must have their docs PRs in a `ready-to-merge` state by the Docs Freeze deadline (April 8th).
For any questions or feedback, please reach out to us on #sig-release.
Unless the KEP changes do not require any updates to the website, please open a PR against the `dev-1.33` branch on `kubernetes/website. ' Instructions to create a placeholder PR are here. All enhancements that are determined to require documentation must have their docs PRs in a `ready-to-merge` state by the Docs Freeze deadline (April 8th).
For any questions or feedback, please reach out to us on #sig-release.
Feature blogs are a great way to spotlight your enhancement and showcase its impact on the community. This is especially encouraged for high-visibility changes as well as deprecations and removals. You can view the current opted-in features on the Comms team’s Github board. If you have opted in, please make sure your blog is ready for review by the Feature Blog Freeze deadline (April 10th).
If you have any questions, please reach out to the comms team in the #release-comms Slack channel!
Best,
Nina Polshakova, on behalf of the v1.33 Release Team.
"...Anyway, what is a fantasy map but a space beyond which There Be Dragons?"
— Terry Pratchett, The Color of Magic
Reply all
Reply to author
Forward
0 new messages