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

Quarterly OWNERS update #793

Merged
merged 1 commit into from
Sep 18, 2019
Merged

Conversation

justaugustus
Copy link
Member

@justaugustus justaugustus commented Sep 18, 2019

Signed-off-by: Stephen Augustus [email protected]

/assign @tpepper @calebamiles
/cc @kubernetes/release-engineering @kubernetes/release-team @kubernetes/licensing

- 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]>
@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject sig/release Categorizes an issue or PR as relevant to SIG Release. labels Sep 18, 2019
@cpanato
Copy link
Member

cpanato commented Sep 18, 2019

/approve

- hoegaarden # Patch Release Team
- idealhack # Patch Release Team
- justaugustus # subproject owner
- tpepper # subproject owner / Patch Release Team
Copy link
Member

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 😇

Copy link
Member Author

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! :)

Copy link
Member

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. :)

Copy link
Member Author

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

Copy link
Member

@idealhack idealhack left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Sep 18, 2019
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@idealhack
Copy link
Member

/hold

in case you want more eyes

@k8s-ci-robot k8s-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 18, 2019
@k8s-ci-robot k8s-ci-robot merged commit 426b990 into kubernetes:master Sep 18, 2019
@k8s-ci-robot k8s-ci-robot added this to the v1.17 milestone Sep 18, 2019
@idealhack
Copy link
Member

@k8s-ci-robot you are too fast 😕

@idealhack idealhack removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. sig/release Categorizes an issue or PR as relevant to SIG Release. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants