[ANNOUNCEMENT] Upcoming Changes to the Kubernetes Release Team
Xander Grzywinski
Hello Kubernetes community!
TL;DR: we’re merging Bug Triage and CI Signal into one subteam under the Release Team. This will result in a lower number of shadows on the team. We don’t anticipate any impact from this to our external stakeholders.
SIG Release is sending out this note to communicate some upcoming changes to the structure of the release team, and changes to the shadow program that will accompany that. This change is internal to the Release Team and should not affect our external stakeholders.
In the past, the release team has comprised of six separate roles. Enhancements, CI Signal, Bug Triage, Release Notes, Documentation, and Communications. Beginning with the 1.30 release cycle, the Bug Triage and CI Signal teams will be merged into a singular team called “Release Signal”. We’ve tried to address some of the questions we expect below.
Why combine these two teams?
Through improvements the release team has made, specifically with the integration of the Github Project board in our workflow, we’re finding that there just typically isn’t enough work to require a full dedicated bug triage team. The flip side of that is that CI Signal is typically quite busy. We see an opportunity here to improve by combining the teams. This is also something we’ve done in the past with the test-infra role, and it’s shown to be successful.
What does this mean for the shadow program?
We’ll put the unfortunate part up front here. This means that there will be a reduction in the total number of shadows on the release team going forward. This comes at a time when the number of applications we get grows higher every release cycle. We are grateful for the interest in our shadow program. Our highest priority has continued to be shipping the most successful release that we possibly can, and we feel this is a path to doing that. There are still many other ways to become active in the project, even within SIG Release.
How will the Release Signal team be built?
This is another aspect that will affect the shadow program. For the 1.30 release cycle (the first with the new team in place), the Release Signal subteam will only be accepting shadows that have previously shadowed or led either CI signal or bug triage. We don’t expect things to stay this way in the future, but as we get this new team figured out, we’d like things to remain as stable as possible. The other subteams will continue to accept new shadows.
Thank you to everyone for taking the time to read this, and for your continued interest in the release team and shadow program. Please reach out to either Xander or Grace on Slack if you have questions. We look forward to shipping a fantastic v1.29 release soon!
Xander Grzywinski - Kubernetes 1.29 Emeritus Advisor
Grace Nguyen - Kubernetes 1.30 Emeritus Advisor
On behalf of SIG-Release
Priyanka Saggu
Exciting news! The "Release Signal" Role Handbook is now up - https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/release-signal/README.md.
Huge thanks to Vyom Yadav for steering the ship!
And a big shoutout to Leonard Pahlke, Maryam Tavakkoli, Paco Xu, Angelos Kolaitis, and Yigit Demirbas for their helpful suggestions and speedy reviews throughout. You folks rock!
This
handbook sets us up for a smooth integration of "CI Signal" & "Bug
Triage" teams into "Release Signal" in the forthcoming Release cycle!
Priyanka Saggu
Kubernetes 1.29 Release Team Lead
On behalf of the 1.29 Release Team
--
You received this message because you are subscribed to the Google Groups "kubernetes-sig-release" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-sig-re...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-sig-release/eb578a8b-fe11-40bc-9bee-581b90c2a3c0n%40kubernetes.io.