sig-release icon indicating copy to clipboard operation
sig-release copied to clipboard

Kubernetes v1.32 Release Highlights contact

Open mbianchidev opened this issue 1 year ago • 9 comments

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?

  1. Pick a group of SIGs to reach out to (listed below), and comment your selection on this issue
  2. Reach out to the SIGs in slack to ask for Release Highlights feedback and directing them to the github discussion using the template below
  3. Comment here when you've completed reaching out to the SIGs

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

  • [x] Node
  • [x] Cloud Provider
  • [x] Architecture
  • [x] Contributor

Group 2 @rytswd

  • [ ] Auth
  • [ ] CLI
  • [ ] K8s Infra
  • [ ] Multicluster

Group 3 @wrkode

  • [ ] API Machinery
  • [ ] Scheduling
  • [ ] Autoscaling
  • [ ] Security
  • [ ] Testing

Group 4 @mbianchidev

  • [x] Network
  • [x] Instrumentation
  • [x] Cluster Lifecycle
  • [x] Docs (not necessary to reach out)
  • [x] Release (not necessary to reach out)

Group 5 @edithturn

  • [ ] Storage
  • [ ] Apps
  • [ ] Windows
  • [ ] UI
  • [ ] Scalability

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

mbianchidev avatar Oct 11 '24 21:10 mbianchidev