Closed leonardpahlke closed 9 months ago
It gives me great pleasure to nominate @Priyankasaggu11929 to be 1.29 Release Team lead. We've worked together in multiple releases and Priyanka was crucial in the release team's effort to migrate to the Github board. Her experience in SIG-Contribex will certainly support her in this role. Priyanka is amazing and I can't wait to see what she and the team accomplishes ð
Thanks for all your hard work @gracenng! So excited to have @Priyankasaggu11929 leading the 1.29 release team. Lets go!!!
Congratulations @Priyankasaggu11929! âĪïļ And thank you @gracenng for all your work for the 1.28 release ððž
Huge congratulations @gracenng, @leonardpahlke and *the entire 1.28 Release team* for a very successful release.
And thank you so much for nominating me. :heart: I'm absolutely honored for the opportunity to lead 1.29 and really excited to get started! :slightly_smiling_face:
Thanks to @gracenng for all the great work from the past 2 years & A big congratulations to @Priyankasaggu11929 for leading V1.29 Release Team.âĪïļ
Having previously engaged in discussions, and listened to her talks, I'm sure the upcoming Release Team is under a great leader like before.
Many congratulations @Priyankasaggu11929 ð Thanks everyone involved in 1.28 Release team, and thanks @gracenng for leading!!
I am delighted to propose @salaxander as the next EA for v1.29. With his experience in various community roles and leading the release team for v1.27 he will be an excellent advisor to the release team. Thanks, Xander ð
Congrats @Priyankasaggu11929; I am very happy and excited that you are stepping into the release lead role ð
I am excited to propose @krol3 as the next Comms Lead for v1.29 ð . Carol has been amazing to work with on v1.28 and has shown great leadership, especially when we were spread over different timezones. She also has experience in many different parts of the release team and k8s project. Thanks Carol!
Congrats @Priyankasaggu11929 ð
/pony party
I feel incredibly privileged to serve as Release Notes Lead for the v1.28
release, and I want to thank the whole release team, the release lead, and especially my amazing shadows for their efforts throughout the cycle.
I'm delighted to nominate @fsmunoz as the Release Notes Lead for v1.29
. Fred's wealth of experience from previous roles in Comms, Enhancements, and Release Notes demonstrates his comprehensive understanding of the Release Team. I believe he will be an excellent lead for the upcoming release!
Congratulations @Priyankasaggu11929 @salaxander :tada:
/pony party
Thank you so very much for the kind words @sanchita-07 , I learned a lot from my participation as a shadow in Release Notes and I'm honoured by the trust you placed upon me. It was really great to learn from you and all the fantastic shadows, and I will do my very best to make 1.29 approach the smoothness of 1.28!
Congrats @Priyankasaggu11929 :fireworks: , it's a pleasure being on your team -- and thank you @gracenng for your leadership in 1.28!
I was honored to serve as a Docs Lead for Kubernetes 1.28, and huge thanks to everyone in the Release Team!
I'm happy to nominate @katcosgrove as the Docs Lead for Kubernetes 1.29. Kat has been a part of the release team since long and I'm sure would do a fantastic job for Docs for 1.29.
Congratulations @Priyankasaggu11929 @salaxander !
/pony party
I had an amazing time representing the Enhancements Team for v1.28, kudos everyone for the successful release!
I'd like to nominate @npolshakova as the Enhancements Lead for the v1.29 release cycle. Nina has been actively contributing as an enhancements shadow since v1.27 and will be a great lead for the upcoming release ð
Also huge congratulations to all the new leads ð
Here goes my honk /honk
@Atharva-Shinde:
Thanks @leonardpahlke!
A huge thank you to @gracenng for leading a successful 1.28 release. I also couldn't imagine a better lead than @Priyankasaggu11929, so I know 1.29 is going to go great as well :)
I was honored to serve as a CI Signal Lead for Kubernetes 1.28. Thank you to the entire 1.28 Release Team for a great release and the excellent ðą Planternetes ðą !
I'd like to nominate @Vyom-Yadav as the Release Signal (named on behalf of merging CI Signal and Bug Triage teams) lead for 1.29! He had served as a shadow for the CI Signal team for both 1.27 and 1.28 and will be an excellent lead for this coming release! âĻ âĻ
Thanks a lot, @mehabhalodiya for the kind words and for placing such trust in me. Being on the previous RTs has taught me a lot about the role, and I'll do everything to keep the standards high.
Thanks a lot @gracenng and @leonardpahlke for your leadership in this release. Looking forward to working under the leadership of @Priyankasaggu11929 and @salaxander!
Missed my honk ð
/honk
@Vyom-Yadav:
Congratulations to @Priyankasaggu11929, @salaxander, and the other new leads! A big shoutout to @gracenng and the team for their amazing work on Planternetes :)
Thanks @Atharva-Shinde! I learned a lot from being an enhancement shadow in the 1.27 and 1.28 releases and am excited for 1.29.
And a huge thanks to @gracenng for leading a successful (and ðą plant-astic ðą) 1.28 release!
Thanks all, with this all team leads have been nominated. @salaxander posted the release team shadow application form a few days ago, below the details! Wish you all a great 1.29 release cycle ð
While the release calendar has not been finalized, here is an overview of the release.
I'm very happy to share that @mehabhalodiya, @mickeyboxell, @neoaggelos and @ramrodo are coming on board with me as the 1.29 Release Lead Shadows. :tada: :confetti_ball:
@gracenng, @leonardpahlke, big thanks for assembling this amazing team of Role Leads for the 1.29 Release cycle, and for your ongoing support as I step into my new responsibilities within the Release Team. :heart: :pray:
And a massive thank you to @salaxander for returning as our Emiratus Advisor for 1.29 â I'm thrilled to start with your guidance. :rocket:
Just a quick update â for the upcoming 1.29 release, we will be maintaining separate roles for CI Signal and Bug Triage teams. During this release cycle, we'll be gradually working on merging the role handbooks to create a guide for the new Release Signal
role.
Once we have the guide ready, we'll send an email to the Kubernetes dev@
and sig-release@
mailing lists within the 1.29 release time-frame to share the details.
Again, big THANK YOU to each of you for your contributions in improving the Release Team processes. :pray:
It was a great experience to be part of the Release Team both in the v1.27 & v1.28 release cycles, learned a lot from the community and people I worked with ð
Also, big thanks to all the v1.28 Bug Triage team shadows for their work and dedication during v1.28.
I am happy to nominate @hailkomputer (Yigit Demirbas) as the Bug Triage Lead for the v1.29 release cycle. Yigit has been active throughout the previous release cycle, contributed a lot as a shadow, and will be a great lead for the upcoming release ð
Thank you @furkatgofurov7! I learned a lot working with you and the release team during v1.28 and I am looking forward to start working with the team for the v1.29.
A big shout out to @gracenng and @leonardpahlke for their leadership during Planternetes release ðŠī âĪïļ .
Congratulations @Priyankasaggu11929! âĪïļ
Just a quick update â for the upcoming 1.29 release, we will be maintaining separate roles for CI Signal and Bug Triage teams. During this release cycle, we'll be gradually working on merging the role handbooks to create a guide for the new
Release Signal
role.
This looks like a nice improvement.
/pony party
Thanks all, with this all team leads have been nominated. @salaxander posted the release team shadow application form a few days ago, below the details! Wish you all a great 1.29 release cycle ð
- Shadow application form
- Release Team Overview: https://git.k8s.io/sig-release/release-team/README.md Release Team Shadows: https://git.k8s.io/sig-release/release-team/shadows.md Selection Criteria: https://git.k8s.io/sig-release/release-team/release-team-selection.md
While the release calendar has not been finalized, here is an overview of the release.
- Release Team Shadow Application Opens: Monday 21st August 2023
- Release Team Shadow Application Closes: Friday 1st September 2023 (23:59 UTC)
- Release Team Shadow Notifications send out latest until: Friday 8th September 2023
- Release Cycle Start: Monday 5th September 2023
- Release Cycle End: Tuesday 5th December (approximate!)
How many times in a year are shadow applications are accepted? Obviously i missed the august chance :) Thanks
Hey, we have three releases a year. You can apply to any of those to shadow a release cycle. We currently assemble the release team for v1.30, I expect to see a form to apply in the next weeks. #2377
/close
@leonardpahlke: Closing this issue.
Hi everyone,
I'm excited to announce that it's time to start assembling the next Kubernetes Release Team 1.29! Thanks, everyone working on 1.28 especially to our amazing Kubernetes Release Team for their dedication and hard work over the past few months.
Please use this issue to nominate the lead for your role on the 1.29 release team. ð Take a look at the Release Team Selection Process docs for details on the process and criteria.
Once role leads are nominated, the upcoming Emeritus Advisor will send out the shadow application survey for selecting 1.29 shadows.
/sig release /area release-team /milestone v1.28 /kind documentation /priority important-soon /assign @leonardpahlke
cc: https://github.com/orgs/kubernetes/teams/sig-release-leads @gracenng