sig-release
sig-release copied to clipboard
Release Manager access for @jeremyrickard and @jrsapi
GitHub Username
@jeremyrickard, @jrsapi
Release Manager role
Release Manager Associate / 1.25 Branch Manager shadows (https://github.com/kubernetes/sig-release/pull/1964)
Tenure
permanent
Release Manager Onboarding
All pull requests within these checklists should be marked with an explicit hold and only released once approved by a Release Engineering subproject owner.
- [x] Addition of a new Release Manager has been discussed with and approved by Release Engineering subproject owners
- [x] Ensure new Release Manager:
- [x] Has joined the following mailing lists:
- [x] Has joined the following Slack channels:
- [x] Is a Kubernetes GitHub org member
- [x] Update Release Managers page to include the new Release Manager: PR https://github.com/kubernetes/website/pull/35003
Release Manager Associate
- [x] Update GitHub teams (
kubernetes/org
): PR https://github.com/kubernetes/org/pull/3556-
milestone-maintainers
-
release-engineering
-
- [x] Update Google Groups/GCP IAM membership (
kubernetes/k8s.io
) PR: https://github.com/kubernetes/k8s.io/pull/3970-
k8s-infra-release-viewers@
-
release-managers@
-
/assign @Verolop @jeremyrickard @jrsapi cc: @kubernetes/release-engineering
I think we've gotten all the checklist covered now. @justaugustus @Verolop did I miss anything?
I think we've gotten all the checklist covered now. @justaugustus @Verolop did I miss anything?
Awesome! For each of the checklist items, can you also provide links to the PRs, for completeness?
Can we close this issue now that both @jeremyrickard and @jrsapi are onboarded?
/kind documentation /priority important-longterm
Checklist is complete. LInks to PRs added. Closing.