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

Assemble Kubernetes 1.15 Release Team #545

Closed
spiffxp opened this issue Mar 14, 2019 · 31 comments

Comments

@spiffxp
Copy link
Member

commented Mar 14, 2019

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

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

tl;dr the current role chooses their successor, this should happen trasnparently

There may be refinements to the process along the way, but I would like to open this issue to get the ball rolling.

I'll open a companion PR to go along with this issue

/sig release
/area release-team
/milestone v1.15

@spiffxp

This comment has been minimized.

Copy link
Member Author

commented Mar 14, 2019

/assign @spiffxp
I'll be pinging the v1.14 roles for their selections

/assign @claurence @tpepper
I've asked @claurence to take the role of Release Lead, and @tpepper to take the role of Release Lead Shadow. This is not intended to setup Tim to take on v1.16, so I would recommend one additional Release Lead Shadow TBD by whatever process @claurence sees fit.

@spiffxp

This comment has been minimized.

Copy link
Member Author

commented Mar 14, 2019

At this point in the process, we're not looking to identify shadows, solely leads.

@spiffxp

This comment has been minimized.

Copy link
Member Author

commented Mar 14, 2019

/assign @justaugustus
You've opened the last three of these, if you have opinions or suggestions on how this should proceed. I may be occupied with getting things out the door as we near the end of the cycle so it would be helpful to have someone not so close to the wire ensure this results in a timely release team

@claurence

This comment has been minimized.

Copy link
Contributor

commented Mar 14, 2019

I'd like to nominate @kacole2 to be enhancements lead for 1.15

@justaugustus

This comment has been minimized.

Copy link
Member

commented Mar 14, 2019

@spiffxp -- I'm on it! Release Team HR is my fave 😍

@nikopen

This comment has been minimized.

Copy link
Member

commented Mar 14, 2019

Happy to nominate Nick Lane @soggiest to lead bug triage for v1.15!

@amwat

This comment has been minimized.

Copy link
Contributor

commented Mar 14, 2019

As discussed in the release team meeting, we'd like to experiment with having a non-googler test infra lead with a confirmed googler co-lead/shadow (who has access to the infrastructure).
To that effect I'd like to nominate @imkin to be the test-infra lead and @Katharine for the co-lead/shadow :)

@lachie83

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

I would like to express interest in the following roles:

  • Release team lead shadow
  • Enhancements shadow
@kacole2

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

thanks @claurence. Happy to accept and help you make another successful Kubernetes release!

@justaugustus

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

I'd like to +1 @lachie83 as an additional Release Team Lead shadow!

@nikopen

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

Having been part of the release team since v1.12 and triage lead in the last two releases, I'm interested in being a Release Lead Shadow.

@hoegaarden

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

I'd like to nominate Cheryl Fong @Bubblemelon to be release branch management lead for v1.15.

@jimangel

This comment has been minimized.

Copy link
Member

commented Mar 15, 2019

I'd like to nominate Barnie (@makoscafee) to be docs lead for 1.15!

@mariantalla

This comment has been minimized.

Copy link
Contributor

commented Mar 15, 2019

I'd like to nominate @alejandrox1 to be the v1.15 CI signal lead.

@justaugustus

This comment has been minimized.

Copy link
Member

commented Mar 16, 2019

The initial PR for the 1.15 Release Team is here: #548

@claurence -- please approve your shadows and that PR when you have a chance.

@dstrebel / @nwoods3 -- please nominate your successors for Release Notes and Communications Lead, respectively.

@nwoods3

This comment has been minimized.

Copy link

commented Mar 18, 2019

I would like to nominate @castrojo for Communications Lead 1.15 and @onlydole @kbarnard10 and I would like to be considered for shadows.

@dstrebel

This comment has been minimized.

Copy link
Contributor

commented Mar 19, 2019

Would like to nominate @onyiny-ang for Release Notes lead for 1.15.

@justaugustus justaugustus added this to Needs Grooming in SIG Release Mar 19, 2019

@claurence

This comment has been minimized.

Copy link
Contributor

commented Mar 20, 2019

I'd like to accept @lachie83 @nikopen and @tpepper as Release Lead shadows for 1.15

@claurence

This comment has been minimized.

Copy link
Contributor

commented Mar 20, 2019

and adding in @jberkus who has expressed interest in being a Lead for Shadows for 1.15. This is a new role whose initial responsibilities would be to support shadows, ensure their success and help with shadow selection.

@jimangel

This comment has been minimized.

Copy link
Member

commented Mar 22, 2019

After doing docs for the past 3 releases, I'm interested in pushing my comfort zone and being a CI Signal Shadow for 1.15.

@krmayankk

This comment has been minimized.

Copy link

commented Mar 26, 2019

i would like to shadow for Enhancements

@mariantalla

This comment has been minimized.

Copy link
Contributor

commented Mar 26, 2019

If there's still space, I'd be interested in shadowing test-infra.

@craiglpeters

This comment has been minimized.

Copy link

commented Mar 26, 2019

I'd like to shadow enhancements 🖐

@claurence

This comment has been minimized.

Copy link
Contributor

commented Mar 26, 2019

Thanks for all the interest in shadowing! We will be sending out a survey again similar to what was done in the 1.14 cycle

@spiffxp - given we're doing a survey for shadows do we need to leave this issue open until shadow selection is done or is getting the lead team enough to close this?

@justaugustus

This comment has been minimized.

Copy link
Member

commented Mar 26, 2019

Let's keep it open until we either close the books on shadows or post a link to the forthcoming survey.

@simplytunde

This comment has been minimized.

Copy link

commented Mar 27, 2019

I am still interested in continuing my role as a doc shadow for 1.15. excited!!!

@jberkus

This comment has been minimized.

Copy link
Contributor

commented Mar 28, 2019

The application from for Shadows is now available! Please fill it out if you're interested in shadowing.

https://forms.gle/qgyvFABJ3RNH95TDA

@simplytunde @craiglpeters @mariantalla @krmayankk @lachie83

@Bubblemelon

This comment has been minimized.

Copy link
Member

commented Apr 8, 2019

@SlickNik would like to continue as a branch management shadow from 1.14 🎉

@denisra

This comment has been minimized.

Copy link

commented Apr 17, 2019

I know I might be a bit late for this release, but I'd like to shadow for the Patch Release Management Team or the Bug Triage if possible.

@justaugustus justaugustus added this to To do in Release Team via automation May 1, 2019

@justaugustus justaugustus removed this from Backlog in SIG Release May 1, 2019

@justaugustus

This comment has been minimized.

Copy link
Member

commented May 1, 2019

This is complete! Thanks to everyone who volunteered!
/close

@k8s-ci-robot

This comment has been minimized.

Copy link
Contributor

commented May 1, 2019

@justaugustus: Closing this issue.

In response to this:

This is complete! Thanks to everyone who volunteered!
/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.

Release Team automation moved this from To do to Done May 1, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.