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.21 Release Team #1363

Closed
lachie83 opened this issue Nov 30, 2020 · 17 comments
Closed

Assemble Kubernetes 1.21 Release Team #1363

lachie83 opened this issue Nov 30, 2020 · 17 comments
Assignees
Labels
area/release-team Issues or PRs related to the release-team subproject needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone

Comments

@lachie83
Copy link
Member

The time is upon us to start assembling the 1.21 release team.

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

At this stage we only require nominations for Role Leads. Once role leads are nominated we will then send out a shadow application survey.

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

cc @justaugustus @saschagrunert @LappleApple

@k8s-ci-robot
Copy link
Contributor

@lachie83: You must be a member of the kubernetes/milestone-maintainers GitHub team to set the milestone. If you believe you should be able to issue the /milestone command, please contact your and have them propose you as an additional delegate for this responsibility.

In response to this:

The time is upon us to start assembling the 1.21 release team.

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

At this stage we only require nominations for Role Leads. Once role leads are nominated we will then send out a shadow application survey.

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

cc @justaugustus @saschagrunert @LappleApple

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.

@k8s-ci-robot k8s-ci-robot added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-team Issues or PRs related to the release-team subproject needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority labels Nov 30, 2020
@lachie83 lachie83 added this to In progress in Release Team Nov 30, 2020
@lachie83
Copy link
Member Author

/assign @lachie83

@jeremyrickard
Copy link
Contributor

Thanks for opening this @lachie83 and thanks so much for your time as EA for the 1.20 release! You've been such an asset.

I would like to nominate @palnabarun as the 1.21 Release Lead! He has done a fantastic job as a shadow and it was a pleasure working with him during this release, and through 1.17, 1.18 and 1.19! I think he will do a great job leading 1.21!

@jeremyrickard
Copy link
Contributor

/milestone v1.21

@k8s-ci-robot k8s-ci-robot added this to the v1.21 milestone Nov 30, 2020
@bai
Copy link
Contributor

bai commented Nov 30, 2020

I'd like to nominate @erismaster as Bug Triage Lead for 1.21. Have a great ride Derrik!

@palnabarun
Copy link
Member

palnabarun commented Nov 30, 2020

Thank you @lachie83 for devoting the time as an EA for this release. 🙂

I would like to nominate @palnabarun as the 1.21 Release Lead! He has done a fantastic job as a shadow and it was a pleasure working with him during this release, and through 1.17, 1.18 and 1.19! I think he will do a great job leading 1.21!

@jeremyrickard -- Thank you for showing confidence in me and guiding us all throughout this release. I am really stoked to be nominated for the role. 😍

@annajung
Copy link
Contributor

I am excited to nominate @reylejano as the lead of the 1.21 Release Docs Team 🎉 🎉

@JamesLaverack
Copy link
Member

I'm very happy to nominate @wilsonehusin as Release Notes Lead for 1.21. 🎉 📓

@RobertKielty
Copy link
Member

RobertKielty commented Dec 1, 2020

I am delighted to nominate @thejoycekung for the role of CI Signal Team Lead for the 1.21 Release of Kubernetes

I would also like to take the opportunity to thank @ScrapCodes @hkamel and @eddiezane for their work on the 1.20 Release. I look forward to working with you all again in the future!

@jrsapi
Copy link
Contributor

jrsapi commented Dec 3, 2020

Excited to nominate @divya-mohan0209 for Comms lead for the 1.21 release cycle.

@divya-mohan0209
Copy link
Contributor

Thank you so much @jrsapi for showing confidence in me and leading by example throughout ! I am super stoked and look forward to serving the community with this role🙏

@kikisdeliveryservice
Copy link
Member

Happy to nominate @annajung for 1.21 Enhancements Lead. ☺️

@lachie83
Copy link
Member Author

lachie83 commented Dec 7, 2020

I would like to nominate @onlydole to serve at Emeritus Advisor for 1.21

@jeremyrickard
Copy link
Contributor

Now that we have the 1.21 Release Team and the Shadows in place, are we good to close this issue @palnabarun @onlydole? Anything outstanding for this one?

🎊

@palnabarun
Copy link
Member

@jeremyrickard @lachie83 -- I'm +1 on closing this. We have a full house! 🎉

@palnabarun
Copy link
Member

Since the team has been finalized. closing this.

/close

@k8s-ci-robot
Copy link
Contributor

@palnabarun: Closing this issue.

In response to this:

Since the team has been finalized. closing this.

/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 In progress to Done (1.20) Feb 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release-team Issues or PRs related to the release-team subproject needs-kind Indicates a PR lacks a `kind/foo` label and requires one. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Development

No branches or pull requests