-
Notifications
You must be signed in to change notification settings - Fork 392
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.
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
Kubernetes v1.32 Release Highlights contact #2640
Comments
/priority important-soon |
I'll take group 1! |
I can take group 5!! :) |
outreach is done! |
I can take group 2 if it isn't taken yet! 🫠 (But I'm open to take any of the groups TBH!) |
It's all taken, once every shadow applies for a group I'll take the remaining one! |
I can take Group 3 |
I've done all my reach-outs, as per below: SIG Auth: https://kubernetes.slack.com/archives/C0EN96KUY/p1729268043204719 I will be updating #2639 once I hear any updates on any of them 👍 |
I've completed all reach-outs for Group 3: SIG API Machinery https://kubernetes.slack.com/archives/C0EG7JC6T/p1729395705977889 |
Good job team on completing the outreach! |
Overview
The release comms team will use this issue to track the work on nudging SIGs for entries on release highlights for the v1.32 release cycle.
Release Highlights discussion for 1.32: #2526 Release Highlights deadline: Tuesday 19th November 2024.
Release Highlights are collected during each release cycle for every SIG to see what should be highlighted in the release blog, webinar, and other communications. Different SIGs have a different number of tracked enhancements. Some SIGs have activities that aren't quite coupled with Kubernetes releases, and it's worth checking with them in case there are things worth calling out in what they did between the previous release and the current release. One example is the Dockershim removal from 1.24 or Immutable Secrets and ConfigMaps from the 1.21 release, as well the cgroup v2 change in 1.31.
What do I need to do?
Depending on the responses we get, we may need to send out a reminder in Slack later in the release cycle to each SIG to get more feedback on Release Highlights Themes.
How do I find a SIG's slack channel?
The Slack channel for each SIG is usually #sig-, but accurate links are available in k/community under sig-list.md. The plan is to ask for responses on the public Slack channel (non-disruptively).
What should I say?
Following is a bootstrap template that you can use to reach out to the individual SIGs informing them about the discussion thread. This template includes the important information to convey to the SIG, but you are free to add your own personalization to the message if you'd like to.
Hello SIG [sig-name],
Release Highlights are an essential part of the Kubernetes release cycle as they provide a birds-eye view of improvements, breaking or user-facing changes that are coming as part of the upcoming release. The release Comms team is asking for your help gathering your Release Highlights for this release. If you have anything to call out, we would appreciate it if your SIG can submit the content in Kubernetes 1.32 Release Highlights GitHub discussion.
Ideally, we would like this to be completed by Tuesday 19th November 2024.
Thank you!
SIG groups
The following are groups of SIGs we need to reach out to. The SIGs are groups together in a mix of those that have tracked enhacements for this release and those that do not. Please comment below with the group you'd like to reach out to.
Group 1 @rashansmith
Group 2 @rytswd
Group 3 @wrkode
Group 4 @mbianchidev
Group 5 @edithturn
We'll try to keep the list up-to-date, but please double-check in the comments if someone has contacted their channel. We can debate more details in Slack.
/milestone v1.32
xref: #2527
The text was updated successfully, but these errors were encountered: