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
OWNERS: Update SIG Release aliases #97700
Conversation
@hasheddan: The label(s) 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. |
/area release-eng |
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.
Add @jeremyrickard in, as he'll be confirmed as TL by EOD tomorrow.
ref: https://groups.google.com/g/kubernetes-dev/c/78E3IobBKH0
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.
@hasheddan -- One more thing...
Can you pull in the changes from #97135?
@justaugustus I believe this is ready to go now 👍 |
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
We're currently only using this for changelog approvals and those should really be handled by relnotes + RelEng. Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: hasheddan <georgedanielmangum@gmail.com> Co-authored-by: Stephen Augustus <foo@auggie.dev>
@hasheddan -- I tweaked some things and updated the description to reflect. cc: @kubernetes/sig-release-leads (for review) For CHANGELOG: /triage accepted |
Also: |
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
For top-level approve: |
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
/approve |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: cpanato, hasheddan, justaugustus, liggitt, saschagrunert, xmudrii 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 |
…700-upstream-release-1.19 Automated cherry pick of #97700: OWNERS: Update SIG Release aliases
…700-upstream-release-1.18 Automated cherry pick of #97700: OWNERS: Update SIG Release aliases
…700-upstream-release-1.20 Automated cherry pick of #97700: OWNERS: Update SIG Release aliases
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
(Edits from @justaugustus...)
Updates SIG Release OWNERS aliases to:
We're currently only using this for changelog approvals and those should
really be handled by relnotes + RelEng.
Includes:
Which issue(s) this PR fixes:
xref kubernetes/sig-release#1322
Special notes for your reviewer:
/assign @justaugustus @saschagrunert
/hold
/sig release
/area release-engineering
cc: @kubernetes/release-engineering
Does this PR introduce a user-facing change?:
Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.: