-
Notifications
You must be signed in to change notification settings - Fork 402
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
Quarterly OWNERS update #793
Conversation
- Prune 1.13 Release Team members - Add 1.17 Release Team role leads - Update Release Engineering OWNERS - Include all Release Engineering subproject OWNERS - Add new Patch Release Team members (dougm + idealhack) - Remove inactive (ixdy, mikedanese) - Add ps882 to Build Admins - Set Release Engineering to own deprecated RT role handbook folders - Remove test-infra-role alias Signed-off-by: Stephen Augustus <[email protected]>
/approve |
- hoegaarden # Patch Release Team | ||
- idealhack # Patch Release Team | ||
- justaugustus # subproject owner | ||
- tpepper # subproject owner / Patch Release Team |
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.
I it somehow possible for me to join release engineering, too? My plan was to continue contributions to the release notes processes from that perspective 😇
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.
@saschagrunert -- I'd be happy to have you working on the Release Engineering side, and definitely appreciate the work you do on release notes today.
To clarify this owner alias, it's the set of contributors who have wide encompassing knowledge of all code that lives within the repo. Currently, that's the Release Engineering subproject owners, which include the SIG Release Chairs and the Patch Release Team.
Folx interested in participating I would expect to become a Release Manager Associate, move into Branch Manager, and then into the Patch Release Team.
We'll look to firmly define the contributor ladder for Release Engineering in 1.17! :)
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.
Ah okay good to know thanks for the clarification. :)
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.
@saschagrunert -- here's the tracking issue for that: #695
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
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, idealhack, justaugustus 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 |
/hold in case you want more eyes |
@k8s-ci-robot you are too fast 😕 |
Signed-off-by: Stephen Augustus [email protected]
/assign @tpepper @calebamiles
/cc @kubernetes/release-engineering @kubernetes/release-team @kubernetes/licensing