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.

• Addition of a new Release Manager has been discussed with and approved by Release Engineering subproject owners
• Ensure new Release Manager:
  • Has joined the following mailing lists:
    • kubernetes-sig-release
    • kubernetes-dev
  • Has joined the following Slack channels:
    • #sig-release
    • #release-management
  • Is a Kubernetes GitHub org member
• Update Release Managers page to include the new Release Manager

Branch Manager

• 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
• (releng: Update Release Managers org#1440) Update GitHub teams (kubernetes/org)
  • milestone-maintainers
  • release-managers
  • release-engineering
  • sig-release
• Update OWNERS
  • (Update Release Managers (take two) #868) kubernetes/sig-release OWNERS_ALIASES
    • Add entry in the branch-managers section
  • (OWNERS: Release Managers updates release#950) kubernetes/release OWNERS_ALIASES
    • Add entry in the branch-managers section
  • (releng: Add Patch Release/Branch Managers as reviewers for SIG Release test-infra#15465) kubernetes/test-infra
    • Add as reviewer for SIG Release OWNERS
• (releng: Release Managers updates k8s.io#481) Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
  • k8s-infra-release-editors@
  • k8s-infra-release-viewers@
  • release-managers@
• Manually grant permission to post on kubernetes-announce
• Manually add to the Release Team Google Group
• (releng: Update release-managers Slack user group community#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: #892 (comment).

[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.