-
Notifications
You must be signed in to change notification settings - Fork 392
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
Update Release Managers (take two) #868
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
/honk |
In response to this:
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. |
+1 honk |
Mostly LGTM, kindly remind that don’t forget to update the GitHub teams :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/lgtm
+1 |
/lgtm |
Discussed any remaining concerns on today's SIG Release call. |
/lgtm I'm concerned we've not sufficiently activated associates (low percentage engagement and promotion to branch manager), especially through active mentorship. With Stephen moving to patch release, and a very busy person, that need for more active mentors fall onto Carlos and Sascha so satisfy relative to the remaining associates. We are a bit top heavy on patch release team, versus branch manager team, and this adds one more to patch release at the cost of one less branch manager. Patch release is fairly low volume work, but since it's higher stakes it may be reasonable to have a solid list of prepared folks well prepared to crank out an urgent release if needed. It's also reasonable for Stephen to practice for a period first hand how the patch release team operations. Maybe we should consider formalizing that patch release managers are also expected to be branch managers now, where they were historically focused on a more trailing set of support tasks? |
- Promote Stephen Augustus to Patch Release Team - Retroactively add Carlos Panato as Branch Manager - Promote Sascha Grunert as Branch Manager - Remove Cheryl Fong as Branch Manager Signed-off-by: Stephen Augustus <saugustus@vmware.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, dougm, guineveresaenger, justaugustus, SlickNik, tpepper The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, thanks again 🙏
...and away we go! 🚀 |
In response to this:
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. |
Proposing the following updates to the Release Managers groups:
Patch Release Team
Branch Managers
Release Manager Associates
Remove inactive associates:
(This reverts commit 8e9c01b, reversing
changes made to e7d102f.)
Signed-off-by: Stephen Augustus saugustus@vmware.com
Supersedes #866 and #867.
I'll leave this to lazy consensus and set a date to merge for Tuesday, December 3rd.
/hold
/assign @tpepper @calebamiles
@kubernetes/sig-release-admins @kubernetes/release-engineering @kubernetes/release-managers
/milestone v1.18
/priority important-longterm
/kind feature cleanup