Chair/Technical Lead access for Sascha and Dan

[justaugustus]

GitHub Username

@saschagrunert @hasheddan
(follow-on to #1321.)

Chair/Technical Lead role

• @saschagrunert (Chair)
• @hasheddan (Technical Lead)

Chair and Technical Lead Onboarding

All pull requests within these checklists should be marked with an explicit
hold and only released once approved by a SIG Release (subproject) owner.

• Addition of a new Release Manager has been discussed with and approved by
  SIG Release owners
• Ensure new Chair/Technical Lead:
  • Has joined the following mailing lists:
    • kubernetes-sig-release
    • kubernetes-release-team
    • kubernetes-dev
    • kubernetes-announce
    • release-managers
    • release-managers-private
  • Has joined the following Slack channels:
    • #sig-release
    • #release-management
  • Is a Kubernetes GitHub org member
  • Is part of the @kubernetes/sig-release-admins GitHub team
• Update Release Managers page to include the new Chair or Technical Lead

Chair/Technical Lead

• Chair/Technical Lead has agreed to abide by the guidelines set forth in
  the Security Release
  Process,
  specifically the embargo on CVE communications.
  (This must be done as an issue comment by the incoming Chair/Technical Lead.)
• Update GitHub teams (kubernetes/org) (Update SIG leadership and Release Managers (promotions, new members, retirement) org#2336)
  • milestone-maintainers
  • release-engineering
  • release-managers
  • sig-release-admins
• Update OWNERS
  • kubernetes/sig-release OWNERS_ALIASES (OWNERS: SIG Release leadership transition and Release Manager updates #1351)
    • Add entry in the sig-release-leads section
  • kubernetes/release OWNERS_ALIASES (OWNERS: Update SIG leadership and Release Managers (promotions, new members, retirement) release#1766)
    • Add entry in the sig-release-leads section
  • kubernetes/test-infra OWNERS_ALIASES (Update sig-release-leads OWNERS_ALIASES test-infra#20372)
    • Add entry in the sig-release-leads section
  • kubernetes/kubernetes OWNERS_ALIASES (OWNERS: Update SIG Release aliases kubernetes#97700)
    • Add entry in the sig-release-approvers section
  • kubernetes/k8s.io OWNERS_ALIASES (Update SIG Release leadership and Release Managers (promotions, new members, retirement) k8s.io#1436)
    • Add entry in the release-engineering-approvers section
• Update SECURITY_CONTACTS
  • kubernetes/release
  • kubernetes/sig-release
• Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
  • leads (members)
  • k8s-infra-release-admins (members)
  • k8s-infra-release-editors (members)
  • release-comms (owners)
  • release-managers (owners)
  • release-managers-private (owners)
• Manually grant permission to post on kubernetes-announce
• Manually add to the Release Team Google Group
• Update Slack release-managers and release-team-leads User Group (kubernetes/community)
• Manually add to the #release-private Slack channel

cc: @kubernetes/sig-release-admins
/assign

[justaugustus]

(Most of this is already done since Dan and Sascha are Release Managers, but opening this to cross the 't's and dot the 'i's.)

[saschagrunert]

@hasheddan do you wanna check what is left open here? I think we just have to double check that everything is in place, right?

[hasheddan]

@saschagrunert yep I'll give this a run-through, thanks!

[saschagrunert]

@hasheddan can we consider this as done?

[hasheddan]

@saschagrunert yep 👍

/close

[k8s-ci-robot]

@hasheddan: Closing this issue.

In response to this:

@saschagrunert yep 👍

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