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

Automated cherry pick of #97700: OWNERS: Update SIG Release aliases #98371

Conversation

hasheddan
Copy link
Contributor

Cherry pick of #97700 on release-1.18.

#97700: OWNERS(sig-release): Remove SIG Release approvers alias

For details on the cherry pick process, see the cherry pick requests page.

justaugustus and others added 7 commits January 25, 2021 10:06
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>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: hasheddan <georgedanielmangum@gmail.com>
Co-authored-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 25, 2021
@k8s-ci-robot k8s-ci-robot added do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 25, 2021
@k8s-ci-robot
Copy link
Contributor

@hasheddan: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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 needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. labels Jan 25, 2021
@hasheddan
Copy link
Contributor Author

/kind cleanup
/release-note-none

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. and removed do-not-merge/release-note-label-needed Indicates that a PR should not merge because it's missing one of the release note labels. do-not-merge/needs-kind Indicates a PR lacks a `kind/foo` label and requires one. labels Jan 25, 2021
@k8s-ci-robot k8s-ci-robot added area/release-eng Issues or PRs related to the Release Engineering subproject sig/release Categorizes an issue or PR as relevant to SIG Release. and removed do-not-merge/needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Jan 25, 2021
@hasheddan
Copy link
Contributor Author

/assign @liggitt

@liggitt
Copy link
Member

liggitt commented Feb 16, 2021

do we want to pick #98701 instead so that sig-release can manage this themselves going forward?

Given we're pulling the relnotes team into review, the changes to
reviewers will happen a little more frequently, which means we'll have
the same issue of needing a top-level approver to do updates that we
were trying to avoid by creating the subdirectory in the first place.

Signed-off-by: Stephen Augustus <foo@auggie.dev>
(cherry picked from commit 5639cd9)
Dan and Sascha are senior Release Managers, SIG Release leadership, and
have already been giving thoughtful reviews of the content in this
directory.

Adding them as reviewers to spread the load of SIG Release eyes on
content.

Signed-off-by: Stephen Augustus <foo@auggie.dev>
(cherry picked from commit 1a43c65)
@hasheddan
Copy link
Contributor Author

@liggitt this has been updated to include #98701, which turned out to be a little cleaner than trying to run a separate cherry-pick of only #98701.

@liggitt
Copy link
Member

liggitt commented Feb 18, 2021

/approve

will leave lgtm to sig-release reviewer

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 18, 2021
@hasheddan
Copy link
Contributor Author

/assign @justaugustus

@justaugustus justaugustus changed the title Automated cherry pick of #97700: OWNERS(sig-release): Remove SIG Release approvers alias Automated cherry pick of #97700: OWNERS: Update SIG Release aliases Feb 20, 2021
@justaugustus
Copy link
Member

/lgtm
/approve

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hasheddan, justaugustus, liggitt

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

@justaugustus justaugustus added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Feb 20, 2021
@k8s-ci-robot k8s-ci-robot removed the do-not-merge/cherry-pick-not-approved Indicates that a PR is not yet approved to merge into a release branch. label Feb 20, 2021
@pacoxu
Copy link
Member

pacoxu commented Feb 20, 2021

/retest

@k8s-ci-robot k8s-ci-robot merged commit 2535543 into kubernetes:release-1.18 Feb 20, 2021
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 cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority Indicates a PR lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. release-note-none Denotes a PR that doesn't merit a release note. 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.

None yet

5 participants