Sig-release: Assemble Kubernetes 1.16 Release Team

Created on 3 Jun 2019  路  29Comments  路  Source: kubernetes/sig-release

Issue for assembling the Kubernetes 1.16 Release Team.

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

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

/sig release
/area release-team
/milestone v.1.16

arerelease-team prioritimportant-soon sirelease

Most helpful comment

Nominaing @idealhack as Branch Manager Lead for v1.16! :tada: :confetti_ball:

All 29 comments

@claurence: The provided milestone is not valid for this repository. Milestones in this repository: [next, v1.15, v1.16]

Use /milestone clear to clear the milestone.

In response to this:

Issue for assembling the Kubernetes 1.16 Release Team.

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

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

/sig release
/area release-team
/milestone v.1.16

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.

/assign @claurence @lachie83

I've asked @lachie83 to take on role of release lead for v.1.16

Thank you very much for considering me for the lead role Claire. I accept your nomination and am excited to serve on the 1.16 release team.

+1 on Lachie

Hail to the new lead!

Happy to continue in the lead team from the breezy shadows during hothot summer 馃尀

pinging @kacole2 @alejandrox1 @Bubblemelon @soggiest @onyiny-ang @imkin @makoscafee ping to remind y'all to nominate successors for your roles here!

I'm going to continue with 1.16 Enhancement Tracking. @mrbobbytables will shadow me once again as well. @craiglpeters has expressed interest in shadowing CI Signal so I would like to put my nomination up for him to be a shadow in that role.

I will love to get in involved as a shadow for this release (first timer!) :)

@raelga the Shadow application will go up probably next week.

I'd like to nominate @onlydole for comms lead for 1.16.

Nominaing @idealhack as Branch Manager Lead for v1.16! :tada: :confetti_ball:

I would like to nominate @simplytunde for Docs Lead for 1.16

I'd like to nominate @onlydole for comms lead for 1.16.

I graciously accept! This group rocks 馃帀

Hey, the CI Signal 1.15 shadows aren't sufficiently available for 1.16 cycle. This means we want to open this up to any prior release shadows, or even prior CI Signal leads, from earlier releases.

@mariantalla @AishSundar @mortent @smourapina @surajnarwade

I would love to shadow CI Signal for 1.16. I'm just about ready to nominate my replacement, as well.

@jberkus , I'm in :smile_cat:

@surajnarwade just to clarify, you鈥檙e ok for being ci signal lead for v1.16?

@alejandrox1 , I have very little experience so I will not be able to lead but I can be shadow and happy to help wherever possible

I am eagerly waiting for the shadow applications. Excited to work in the team. :smile:

PS: I am a first timer.

@surajnarwade ah alright, not a problem.
just wanted to clarify @jberkus 鈥榮 message: right now we are looking for someone to take ci signal shadow as it is discouraged for a lead to be a lead for two consecutive cycles.

As a few have mentioned on the thread, we are currently staffing the role leads for the 1.16 cycle.
As soon as all lead positions are nominated and staffed AND the updated questionnaire is complete, we will notify both here and on kubernetes-dev.

Thanks everyone for your interest so far! :)

/milestone v1.15
/priority important-soon

I nominate @xmudrii for Bug Triage lead for 1.16

I'd like to nominate @saschagrunert for Release Notes lead--he's taken the shadow role to a whole new level this release and will be a great lead for 1.16 (in which we expect to see the release notes completel the move to a new format: https://github.com/kubernetes-sigs/release-notes)

The Release team Shadow Questionnaire is now ready.

Shadows, start your applications!

@surajnarwade @palnabarun @raelga

I guess its good to close this now.

I think this should stay open till @justaugustus has sent out feedback/messages to the unselected shadows.

That's the final loop to close on this.

This is now complete.
Thank you everyone who volunteered! :)

/close

@justaugustus: Closing this issue.

In response to this:

This is now complete.
Thank you 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.

Was this page helpful?
0 / 5 - 0 ratings