Sig-release: Assemble Kubernetes 1.13 Release Team

[justaugustus]

This is the official issue for assembling the Kubernetes 1.13 Release Team.

Please review the Release Team Selection docs for details on the process and criteria.

We will echo our nominations here, for anyone who wants to follow the thread, instead of attending the meeting.

Additionally, we will accept volunteers for Release Team role shadows here.

The initial PR for the 1.13 Release Team can be found here: https://github.com/kubernetes/sig-release/pull/279

---

The announcement was made here on kubernetes-milestone-burndown and will be mentioned in tomorrow's (9/6) Kubernetes Community Meeting.

1.13 Release Team Nominations

• When: Monday, 9/10, 10 am PST
• Where: 1.12 Release team meeting

Present and discuss nominations with Sig-Release

• When: Tuesday, 9/11, 2 pm PST
• Where: SIG Release Biweekly

/sig release
cc: @tpepper @AishSundar @calebamiles @jdumars

[justaugustus]

I'd like to formally nominate Kendrick Coleman (@kacole2) for 1.13 Features Lead.
He's done phenomenal work and has been my right hand during the 1.12 release cycle! :heart:

[AishSundar]

From offline discussion, I am delighted that Aaron Crickenberger (@spiffxp) has kindly agreed to be the release lead shadow for 1.13 ! Woohoo

[justaugustus]

Awesome! 1.13, now with moar SIG Beard! Added to the PR.

[justaugustus]

/assign @AishSundar @justaugustus

[shivanimall]

Release Team Selection doc leads to 404

[idealhack]

@shivani1494 Thanks, fixed

[wadadli]

I'd like to be a feature shadow.

[shivanimall]

I'd like to be a CI shadow! Thanks!

[krzyzacy]

@amwat wanna take test-infra role for 1.13? maybe @Katharine can share some shadow fun? :-)

[amwat]

Probably @cjwagner can take up the lead again for all the Tide related stuff?
I'd like to be test-infra shadow.

[cjwagner]

Since 1.13 will be the first release handled from start to finish by Tide, it would probably be helpful for me to be the test-infra lead to work out any kinks and document the process in detail.

[imkin]

Nominate myself for the branch manager shadow :-)

[jimangel]

I formally nominate Tim Fogarty @tfogo as Docs Lead and would like to volunteer as a shadow again! Thanks!

cc: @zparnold

[guineveresaenger]

I'm proud to nominate Niko Penteridis @nikopen as Bug Triage Lead.

I also would like to volunteer as tribute for CI or Features Shadow.

[marpaia]

I'd like to nominate myself to be Release Notes Lead 😸

[sumitranr]

I nominate myself for a branch manager shadow

[justaugustus]

I've added a first round of people to the PR.
If your name isn't on the sheet yet, don't fret. We just need to have the official nominations first and set all of the Lead roles, before adding new shadows.

Thanks to everyone who has volunteered already!! :heart:

[AishSundar]

Following offline discussions I would like to nominate @jberkus for the CI lead role for 1.13 !!

[calebamiles]

@justaugustus please add @aleksandra-malinowska as the patch release manager

[AishSundar]

I would like to nominate @dougm to stay on as the 1.13 branch manager lead. Both @tpepper and @dougm have made numerous improvements in 1.12 to pilot and update the branch manager playbook in efforts to open up the role to anyone outside Google. There are still a few loops to close and the changes need to stabilize a bit more. Having @dougm continue in the role will give enough time to test drive it a bit more before opening it out at large.

[mortent]

I would like to volunteer as CI shadow

[idealhack]

I would like to continue the role as a branch manager shadow in 1.13.

[ameukam]

I would like to volunteer as Features Shadow.

[zparnold]

@jimangel @tfogo I'd be happy to shadow/mentor if need be. 😄

[thanasisk]

I would like to volunteer as Bug Triage shadow

[hoegaarden]

I would like to continue as a branch manager shadow and also nominate myself for test-infra shadow.

[mohammedzee1000]

I would like to shadow the bug triage/ci signal role.

[shubheksha]

I'd like to shadow bug triage/features 😄

[kbarnard10]

I'd like to volunteer for Comms Lead :)

[AishSundar]

Thanks all for volunteering both in this issue and in the release team call this morning. Here's a roundup of the nominations thus far. If I have missed someone please comment below. @justaugustus has kindly agreed to roll this list into the PR later today.

Role | Lead | Shadow(s)
-- | -- | --
Lead | Aishwarya Sundar (@AishSundar) | Aaron Crickenbecker (@Spiffxp)
Enhancements | Kendrick Coleman (@kacole2) | Michael Singh (@wadadli), Guinevere Saenger (@guineveresaenger/ @gsaenger on Slack), Arnaud Meukam (@ameukam)
CI Signal | Josh Berkus (jberkus) | Shivaani Mall (@shivani1494 ), Morten Torkildsen (@mortent)
Test Infra | Cole Wagner (@cjwagner) | Amit Watve (@amwat), Hannes Hoerl (@hoegaarden)
Bug Triage | Niko Penteridis (@nikopen) | Mohammed (@mohammedzee1000 ), Athanasios Kostopoulos (@thanasisk), Shubheksha (@shubheksha)
Branch Manager | Doug MacEachern (@dougm)? | Yang Li (@idealhack), Hannes Hoerl (@hoegaarden), Dhawal Yogesh Bhanushali(@imkin), Sumitran Raghunathan (@sumitranr)
Docs | Tim Fogarty (@tfogo) | Jim Angel (@jimangel), Zach Arnold (@zparnold)
Release Notes | Mike Arpaia (@marpaia) | Dave Strebel (@dstrebel)
Communications | Kaitlyn Barnard (@kbarnard10) | Kristen Evans (@kristenevans)
Patch Release Manager/ Team | Aleksandra Malinowska (@aleksandra-malinowska ) and Tim Pepper (@tpepper)

[tao12345666333]

I would like to volunteer as CI shadow (or any other team that needs people).Thanks.

[justaugustus]

Thanks @AishSundar for including the results of yesterday's Release Team meeting here! I've updated #279 to reflect the candidates we nominated, so that is ready to merge. :)

[mariantalla]

I'd be very interested to shadow CI signal (and/or any other team that needs people, of course; but do have a soft spot for CI :) ).

[claurence]

I would be interested in shadowing the patch release manager or enhancements

[npentrel]

I'd like to shadow @tfogo with the docs if that's still possible!

[AishSundar]

Thanks for the interest everyone. As per guidance from Sig Release we are capping shadows to 4 per role, except for Branch Manager which will be capped at 2. I will work with @justaugustus to process the nominations thus far and update the release team accordingly.

[justaugustus]

I've pushed a new PR which includes our additional volunteers: #291

Here are the shadows roles that we have left:

• (2) Test infra
• (1) Bug Triage
• (1) Docs
• (3) Communications

[makoscafee]

Hi, I would like to shadow docs if possible.

[simplytunde]

@justaugustus I would love to shadow Test infra or Bug Triage

[conradwt]

@justaugustus I would be interested in shadowing the Test infra or Communications roles.

[RahulMahale]

@justaugustus I would love to be part of Test Infra or Patch Release Manager/ Team. Let me know what is good place to start.

[sahitpj]

Hi, I would like to shadow Communications or Test Infra if possible @justaugustus

[pigletfly]

I would like to shadow Test infra if possible.

[boluisa]

@justaugustus I will love to shadow test infra or bug triage

[castrojo]

I can shadow Release Notes and Communications if you're still looking for people!

[srajappa]

I will be delighted to shadow _TEST-INFRA_ role.

If that's not possible then I can shadow on _COMMUNICATIONS_ role.

[tfogo]

Hi @MAKOSCAFEE, I'm excited that you'll be shadowing Docs for the 1.13 release. Can you message me on the Kubernetes slack (@tfogo)?

[makoscafee]

Hi @tfogo sure let me message you.

[justaugustus]

@castrojo / @srajappa -- I've slotted you for Comms here: https://github.com/kubernetes/sig-release/pull/306

@pigletfly / @boluisa -- The roles you selected already have 4 shadows, but we still have room to shadow Release Notes. Would you like to do that instead?

[boluisa]

@justaugustus Yes I will like to shadow release notes.

[pigletfly]

@justaugustus Sure, I'd like to.

[justaugustus]

Hey everyone,

Thank you so much for volunteering for the Kubernetes 1.13 Release Team!
Anyone who posted here should have a role; please check the roster to ensure your contact info is accurate.

To participate in the Release Team, you may occassionally need magic powers, which come from being a Kubernetes GitHub organization member.

Here are a few useful resources to help you along in that journey:

• Community Membership
• Kubernetes Contributor Guide
• Kubernetes Cheat Sheet
• Understanding the release process

...and some useful Slack channels:

• #sig-contribex (Contributor Experience)
• #sig-release (For Release activities)
• #kubernetes-dev
• #kubernetes-users
• #kubernetes-teachers
• #kubernetes-novice
• #meet-our-contributors

I would suggest proactively reaching out to your role lead to get a jump on the process and learn how you can best contribute.

Happy shipping!

/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

Hey everyone,

Thank you so much for volunteering for the Kubernetes 1.13 Release Team!
Anyone who posted here should have a role; please check the roster to ensure your contact info is accurate.

To participate in the Release Team, you may occassionally need magic powers, which come from being a Kubernetes GitHub organization member.

Here are a few useful resources to help you along in that journey:

• Community Membership
• Kubernetes Contributor Guide
• Kubernetes Cheat Sheet
• Understanding the release process

...and some useful Slack channels:

• #sig-contribex (Contributor Experience)
• #sig-release (For Release activities)
• #kubernetes-dev
• #kubernetes-users
• #kubernetes-teachers
• #kubernetes-novice
• #meet-our-contributors

I would suggest proactively reaching out to your role lead to get a jump on the process and learn how you can best contribute.

Happy shipping!

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.