Sig-release: Release Manager access for @saschagrunert

[saschagrunert]

GitHub Username

@saschagrunert

Release Manager role

Branch Manager

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:
  
  
  • kubernetes-sig-release
  
  
  • kubernetes-dev
  
  
  • [X] Has joined the following Slack channels:
  
  
  • #sig-release
  
  
  • #release-management
  
  
  • [X] Is a Kubernetes GitHub org member
  
  
• [X] Update Release Managers page to include the new Release Manager

Branch Manager

• [x] Release Manager has agreed (on this issue) to abide by the guidelines set forth in the
  Security Release Process,
  specifically the embargo on CVE communications
• [x] (https://github.com/kubernetes/org/pull/1440) Update GitHub teams (kubernetes/org)
  
  
  
  • milestone-maintainers
  
  
  • release-managers
  
  
  • release-engineering
  
  
  • sig-release
  
  
• [x] Update OWNERS
  
  
  
  • (https://github.com/kubernetes/sig-release/pull/868) kubernetes/sig-release OWNERS_ALIASES
  
  
  • Add entry in the branch-managers section
  
  
  • (https://github.com/kubernetes/release/pull/950) kubernetes/release OWNERS_ALIASES
  
  
  • Add entry in the branch-managers section
  
  
  • (https://github.com/kubernetes/test-infra/pull/15465) kubernetes/test-infra
  
  
  • Add as reviewer for SIG Release OWNERS
  
  
• [x] (https://github.com/kubernetes/k8s.io/pull/481) Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
  
  
  
  • k8s-infra-release-editors@
  
  
  • k8s-infra-release-viewers@
  
  
  • release-managers@
  
  
• [x] Manually grant permission to post on kubernetes-announce
• [x] Manually add to the Release Team Google Group
• [x] (https://github.com/kubernetes/community/pull/4284) Update Slack release-managers User Group (kubernetes/community)

cc: @kubernetes/release-engineering

[saschagrunert]

/assign @justaugustus

[justaugustus]

@saschagrunert -- Before I can close this out, I just need you to agree to the security release process in an issue comment, like this: https://github.com/kubernetes/sig-release/issues/892#issuecomment-562571918.

[saschagrunert]

I've read the Security Release Process and I agree to uphold it and the security embargo.

[saschagrunert]

All accesses to the google groups look good as well now. :)

[justaugustus]

Thanks Sascha!
/close

[k8s-ci-robot]

@justaugustus: Closing this issue.

In response to this:

Thanks Sascha!
/close

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.