Sig-release: Release Team Lead access for @savitharaghunathan @kikisdeliveryservice @divya-mohan0209 @annajung @erismaster

[savitharaghunathan]

GitHub Username(s)

• @annajung
• @divya-mohan0209
• @erismaster
• @kikisdeliveryservice
• @savitharaghunathan

Release Cycle

Kubernetes 1.22

Prerequisites

• [x] Ensure new Release Team Lead:
  
  
  
  • [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] Has completed the CNCF Inclusive Speaker Orientation
  
  

Onboarding

• [x] Release Team 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 Release Team Lead.
• [x] Update GitHub teams (kubernetes/org)
  
  
  
  • milestone-maintainers
  
  
  • release-team
  
  
  • release-team-leads
  
  
  • sig-release
  
  
• [x] Update kubernetes/sig-release OWNERS
  
  
  
  • Release Team Lead and Shadows
  
  
  • Add an approvers entry in releases/release-x.y/OWNERS
  
  
  • Release Team Lead only
  
  
  • In OWNERS_ALIASES, add an entry in the following sections:
    
    
    
    
    
    • release-team
    
    
    
    • release-team-lead-role
    
    
    
  
  
• [x] Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
  
  
  
  • k8s-infra-release-viewers@
  
  
  • release-managers@
  
  
• [x] Manually grant access on the following Google Groups:
  
  
  
  • kubernetes-release-team (Add as Manager)
  
  
  • kubernetes-sig-leads (Add as Member)
  
  
• [x] Grant calendar access
• [x] Grant Zoom credentials (host key)
• [x] Add incoming leads to release-team-leads Slack Group (kubernetes/community)
  
  
  
  • Add slack ID(s) to users.yaml, if they are not yet in the file
  
  
  • Add username(s) to usergroups.yaml
  
  

Offboarding

• [ ] Remove from GitHub teams (kubernetes/org)
  
  
  
  • milestone-maintainers
  
  
  • release-team
  
  
  • release-team-leads
  
  
• [ ] Remove from Google Groups/GCP IAM membership (kubernetes/k8s.io)
  
  
  
  • k8s-infra-release-viewers@
  
  
  • release-managers@
  
  
• [ ] Manually remove from the following Google Groups:
  
  
  
  • kubernetes-release-team (Add as Manager)
  
  
  • kubernetes-sig-leads (Add as Member)
  
  
• [ ] Remove from release-team-leads Slack Group (kubernetes/community)
  
  
  
  • Remove slack ID(s) from users.yaml, if no longer in a group
  
  
  • Remove username(s) from usergroups.yaml
  
  

cc: @kubernetes/release-engineering @kubernetes/release-team

/milestone v1.22

[savitharaghunathan]

I have completed the CNCF Inclusive Speaker Orientation training! Here's my certificate id: LF-a7hzkmrc4m

✨ I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[savitharaghunathan]

/kind documentation
/priority important-soon

[divya-mohan0209]

I have completed the CNCF Inclusive Speaker Orientation training! Here's my certificate id: LF-cuyg856pxb

✨ I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[annajung]

I have completed the CNCF Inclusive Speaker Orientation training: LF-j7l070r0il

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[erismaster]

I have completed the CNCF Inclusive Speaker Orientation training: LF-xah4uwsvqv

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[kikisdeliveryservice]

I completed my training: LF-tst9jc3b5s

I solemnly swear to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.