Sig-release: Technical Lead access for @cpanato and @puerco

[justaugustus]

GitHub Username

@cpanato @puerco

Chair/Technical Lead role

Technical Lead
ref: https://github.com/kubernetes/community/pull/5807

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.

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

Chair/Technical Lead

• [x] 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.)
• [x] Update GitHub teams (kubernetes/org) - https://github.com/kubernetes/org/pull/2782
  
  
  
  • milestone-maintainers
  
  
  • release-engineering
  
  
  • release-managers
  
  
  • sig-release-admins
  
  
• [x] Update OWNERS
  
  
  
  • [x] kubernetes/sig-release OWNERS_ALIASES - https://github.com/kubernetes/sig-release/pull/1592
  
  
  • Add entry in the sig-release-leads section
  
  
  • [x] kubernetes/release OWNERS_ALIASES - https://github.com/kubernetes/release/pull/2120
  
  
  • Add entry in the sig-release-leads section
  
  
  • [x] kubernetes/test-infra OWNERS_ALIASES - https://github.com/kubernetes/test-infra/pull/22530
  
  
  • Add entry in the sig-release-leads section
  
  
  • [x] kubernetes/kubernetes OWNERS_ALIASES - https://github.com/kubernetes/kubernetes/pull/102811
  
  
  • Add entry in the release-engineering-approvers section
  
  
  • [x] kubernetes/k8s.io OWNERS_ALIASES - https://github.com/kubernetes/k8s.io/pull/2198
  
  
  • Add entry in the release-engineering-approvers/sig-release-leads section
  
  
• [x] Update SECURITY_CONTACTS
  
  
  
  • [x] kubernetes/release - https://github.com/kubernetes/release/pull/2120
  
  
  • [x] kubernetes/sig-release - https://github.com/kubernetes/sig-release/pull/1592
  
  
• [x] Update Google Groups/GCP IAM membership (kubernetes/k8s.io) - https://github.com/kubernetes/k8s.io/pull/2214
  
  
  
  • leads (members)
  
  
  • k8s-infra-release-admins (members)
  
  
  • k8s-infra-release-editors (members)
  
  
  • release-comms (owners)
  
  
  • release-managers (owners)
  
  
  • release-managers-private (owners)
  
  
• [x] Manually grant permission to post on kubernetes-announce
• [x] Manually add to the Release Team Google Group
• [x] Update Slack release-managers and release-team-leads User Group (kubernetes/community) https://github.com/kubernetes/community/pull/5836
• [x] ~Manually add to the #release-private Slack channel~ (channel has been archived)

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

[cpanato]

Will prepare some PRs and other items that need a subscription or just check if we are in those lists I will sync with @puerco to double check

[saschagrunert]

Added @cpanato and @puerco to the kubernetes-release-team mailing list. :heavy_check_mark:

[cpanato]

I do hereby agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[justaugustus]

Confirming that both Carlos and Adolfo already agree to the security embargo as part of their Release Manager roles. :)

[puerco]

I do hereby agree to abide by the guidelines set forth in the Security Release Process, specifically the embargo on CVE communications.

[cpanato]

all tasks are done!
/close

[k8s-ci-robot]

@cpanato: Closing this issue.

In response to this:

all tasks are done!
/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.