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.

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

Open
23 tasks done
mbianchidev opened this issue Oct 11, 2024 · 10 comments
Open
23 tasks done

Kubernetes v1.32 Release Highlights contact #2640

mbianchidev opened this issue Oct 11, 2024 · 10 comments
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@mbianchidev
Copy link
Member

mbianchidev commented Oct 11, 2024

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

  • Node
  • Cloud Provider
  • Architecture
  • Contributor

Group 2 @rytswd

  • Auth
  • CLI
  • K8s Infra
  • Multicluster

Group 3 @wrkode

  • API Machinery
  • Scheduling
  • Autoscaling
  • Security
  • Testing

Group 4 @mbianchidev

  • Network
  • Instrumentation
  • Cluster Lifecycle
  • Docs (not necessary to reach out)
  • 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 mbianchidev added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Oct 11, 2024
@k8s-ci-robot k8s-ci-robot added this to the v1.32 milestone Oct 11, 2024
@k8s-ci-robot k8s-ci-robot added needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Oct 11, 2024
@mbianchidev
Copy link
Member Author

/priority important-soon
/kind documentation
/area release-team

@k8s-ci-robot k8s-ci-robot added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. kind/documentation Categorizes issue or PR as related to documentation. area/release-team Issues or PRs related to the release-team subproject and removed needs-priority needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Oct 11, 2024
@rashansmith
Copy link
Contributor

I'll take group 1!

@edithturn
Copy link

I can take group 5!! :)

@rashansmith
Copy link
Contributor

I'll take group 1!

outreach is done!

@rytswd
Copy link
Member

rytswd commented Oct 14, 2024

I can take group 2 if it isn't taken yet! 🫠 (But I'm open to take any of the groups TBH!)

@mbianchidev
Copy link
Member Author

It's all taken, once every shadow applies for a group I'll take the remaining one!

@wrkode
Copy link

wrkode commented Oct 17, 2024

I can take Group 3

@rytswd
Copy link
Member

rytswd commented Oct 18, 2024

I've done all my reach-outs, as per below:

SIG Auth: https://kubernetes.slack.com/archives/C0EN96KUY/p1729268043204719
SIG CLI: https://kubernetes.slack.com/archives/C2GL57FJ4/p1729268176802849
SIG K8s Infra: https://kubernetes.slack.com/archives/CCK68P2Q2/p1729268333281389
SIG Multicluster: https://kubernetes.slack.com/archives/C09R1PJR3/p1729268450185009

I will be updating #2639 once I hear any updates on any of them 👍

@wrkode
Copy link

wrkode commented Oct 20, 2024

@mbianchidev
Copy link
Member Author

Good job team on completing the outreach!
Now we wait for the opt-in and keep the discussion updated :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject kind/documentation Categorizes issue or PR as related to documentation. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests

6 participants