KEMBAR78
OWNERS cleanup (Release Team's version) by justaugustus · Pull Request #2865 · kubernetes/sig-release · GitHub
Skip to content

Conversation

@justaugustus
Copy link
Member

@justaugustus justaugustus commented Sep 14, 2025

What type of PR is this:

/kind cleanup documentation

What this PR does / why we need it:

This is the first part of our access control review, tracked in #2864.
In this PR, we dramatically simplify the @kubernetes/release-team OWNERS entries to keep things tidy and accelerate reviews in the respective areas.

cc: @kubernetes/sig-release-leads @katcosgrove @drewhagen

Here's a detailed changelog:

  • Prune deprecated roles & remove associated subdirectory files

    Removes the following deprecated roles:

    • build-admins (Release Engineering)
    • ci-signal-role (Release Team)
    • bug-triage-role (Release Team)
    • release-notes-role (Release Team)

    Also removed are any subdirectory OWNERS files in which the deprecated role was the only entry.

  • Initial update of all top-level Release Team aliases

    • Prune previous Release Team leads (thanks for your leadership!)
    • Move v1.35 subteam role members to aliases
  • Offboard Grace as Release Team subproject lead

  • Refactor Release Team aliases to match the other entries

    • Append -approvers to aliases
    • Include -subteam in aliases referencing subteams
    • Lexicographic sort for subteam aliases
  • Sync all Release Team aliases for current cycle

    • Subproject lead only has membership for -approvers alias
      (which already has access to the appropriate directories)
    • Create release-team-lead-shadows alias
    • Move RT lead shadows to top-level alias
  • Add explicit reviewers for Release Team top-level dirs

    ...also deletes the RT Lead handbooks OWNERS file, since it's now superfluous.

  • Add RT Lead Shadows as Release Team top-level dirs reviewers

  • Prune files from previous releases

  • Remove RT Lead and add SIG Release leads to top-level reviewers

Signed-off-by: Stephen Augustus foo@auggie.dev

Which issue(s) this PR fixes:

Special notes for your reviewer:

This one would be good to review commit-by-commit, as there are a few spacing and positional changes of entries that may make the combined diff a little difficult to parse.

Removes the following deprecated roles:

- build-admins (Release Engineering)
- ci-signal-role (Release Team)
- bug-triage-role (Release Team)
- release-notes-role (Release Team)

Also removed are any subdirectory OWNERS files in which the deprecated
role was the only entry.

Signed-off-by: Stephen Augustus <foo@auggie.dev>
- Prune previous Release Team leads (thanks for your leadership!)
- Move v1.35 subteam role members to aliases

Signed-off-by: Stephen Augustus <foo@auggie.dev>
Signed-off-by: Stephen Augustus <foo@auggie.dev>
- Append `-approvers` to aliases
- Include `-subteam` in aliases referencing subteams
- Lexicographic sort for subteam aliases

Signed-off-by: Stephen Augustus <foo@auggie.dev>
- Subproject lead only has membership for `-approvers` alias
  (which already has access to the appropriate directories)
- Create `release-team-lead-shadows` alias
- Move RT lead shadows to top-level alias

Signed-off-by: Stephen Augustus <foo@auggie.dev>
...also deletes the RT Lead handbooks OWNERS file, since it's now
superfluous.

Signed-off-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 kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. area/release-eng Issues or PRs related to the Release Engineering subproject needs-priority area/release-team Issues or PRs related to the release-team subproject sig/release Categorizes an issue or PR as relevant to SIG Release. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Sep 14, 2025
@k8s-ci-robot k8s-ci-robot added the size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. label Sep 14, 2025
@justaugustus
Copy link
Member Author

I'm not really sure why the bot made the reviewers selections it did, but:
/uncc @Atharva-Shinde @bradmccoydev
/assign @kubernetes/sig-release-leads

@justaugustus
Copy link
Member Author

Signed-off-by: Stephen Augustus <foo@auggie.dev>
@Vyom-Yadav
Copy link
Member

Just so that it can be fixed after this PR is merged, this will require updates to the release lead template: (I won't cover it in my updates until this PR is merged)

- [ ] Updated `kubernetes/sig-release` `OWNERS`
- Release Team Lead and Shadows
- Add an `approvers` entry in `releases/release-1.XX/OWNERS`
- **Release Team Lead only**
- In `OWNERS_ALIASES`, add an entry in the following sections:
- `release-team`
- `release-team-lead-role`

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato, 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:
  • OWNERS [cpanato,justaugustus]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot merged commit 24c94f0 into kubernetes:master Sep 14, 2025
2 checks passed
@k8s-ci-robot k8s-ci-robot added this to the v1.35 milestone Sep 14, 2025
@justaugustus
Copy link
Member Author

Just so that it can be fixed after this PR is merged, this will require updates to the release lead template: (I won't cover it in my updates until this PR is merged)

Continuing the convo here: #2864 (comment)

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. kind/cleanup Categorizes issue or PR as related to cleaning up code, process, or technical debt. kind/documentation Categorizes issue or PR as related to documentation. lgtm "Looks good to me", indicates that a PR is ready to be merged. needs-priority sig/release Categorizes an issue or PR as relevant to SIG Release. size/XL Denotes a PR that changes 500-999 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants