Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Release Team Lead access for alejandrox1, mrbobbytables, and onlydole #933

Closed
14 tasks done
alejandrox1 opened this issue Jan 2, 2020 · 25 comments
Closed
14 tasks done

Release Team Lead access for alejandrox1, mrbobbytables, and onlydole #933

alejandrox1 opened this issue Jan 2, 2020 · 25 comments
Assignees
@justaugustus @alejandrox1
Labels
area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Milestone
v1.18

Comments

@alejandrox1
Copy link
Contributor

alejandrox1 commented Jan 2, 2020 •
edited by justaugustus
Loading

GitHub Username(s)

Release Cycle

Kubernetes 1.18

Prerequisites

Onboarding

  • 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.
  • Update GitHub teams (kubernetes/org)
    • milestone-maintainers
    • release-team
    • release-team-leads
    • sig-release
  • 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
  • Update Google Groups/GCP IAM membership (kubernetes/k8s.io)
    • k8s-infra-release-viewers@
    • release-managers@
  • Manually grant access on the following Google Groups:
  • Grant calendar access
  • Grant Zoom credentials (host key)

Offboarding

cc: @kubernetes/release-engineering @kubernetes/release-team
@alejandrox1 alejandrox1 added sig/release Categorizes an issue or PR as relevant to SIG Release. area/release-team Issues or PRs related to the release-team subproject area/release-eng Issues or PRs related to the Release Engineering subproject labels Jan 2, 2020
@alejandrox1 alejandrox1 self-assigned this Jan 2, 2020
@alejandrox1
Copy link
Contributor Author

/milestone v1.18
/priority critical-urgent

@k8s-ci-robot k8s-ci-robot added the priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. label Jan 2, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Jan 2, 2020
@alejandrox1
Copy link
Contributor Author

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

@justaugustus
Copy link
Member

@alejandrox1 -- Can you add your username to this list and update the issue title to include your usernames?

Also, do you want to take care of the PRs and then tag me for review?
/assign @justaugustus @alejandrox1

@alejandrox1
Copy link
Contributor Author

@justaugustus yes (will update with usernames) and yes will take care of PRs as we speak.
Will ping you when this is ready

@alejandrox1 alejandrox1 mentioned this issue Jan 2, 2020
Merged
@alejandrox1 alejandrox1 changed the title Release Team Lead access for <GH-handle> Release Team Lead access for alejandrox1, daminisatya, and mrbobbytables Jan 2, 2020
This was referenced Jan 2, 2020
Merged
Merged
@alejandrox1
Copy link
Contributor Author

As per the offboarding part of the template, I converted @guineveresaenger @jeefy and @mariantalla into members of the kubernetes-release-team google group.

@alejandrox1
Copy link
Contributor Author

As per the onboarding section of the template, I made @daminisatya and @mrbobbytables managers of the kubernetes-sig-leads google group.

However, all 3 of us need to be added as members of kubernetes-sig-leads

This was referenced Jan 3, 2020
Closed
Merged
@alejandrox1
Copy link
Contributor Author

Updates on this (for the couple things that are not waiting for review)...

Manually remove from the following Google Groups:

  • kubernetes-release-team (Add as Manager)
  • kubernetes-sig-leads (Add as Member)

I added @mrbobbytables and @daminisatya as managers to kubernetes-release-team and off-boarded the previous rt lead and shadows.
Just need to add and remove people from kubernetes-sig-leads.

Also, need access to the calendar and may be host key for zoom (I have the one from previous cycle).
/cc @justaugustus @tpepper

@justaugustus
Copy link
Member

@alejandrox1 -- Looks like we've got most things squared away here, but I just want to confirm with you.

@mrbobbytables @daminisatya -- You still need to comment that you're aware of and agree to uphold the Security Release Process (example).

@mrbobbytables
Copy link
Member

Ah, my bad^^:;;;;

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

/pony salute

@k8s-ci-robot
Copy link
Contributor

@mrbobbytables: pony image

In response to this:

Ah, my bad^^:;;;;

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

/pony salute

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.

@justaugustus justaugustus added lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. and removed priority/critical-urgent Highest priority. Must be actively worked on as someone's top priority right now. labels Jan 12, 2020
@alejandrox1
Copy link
Contributor Author

@justaugustus seems like onboarding part is good to go pending @daminisatya going through the security releaseprocess.

Offboarding part, need to follow up on kubernetes/org#1513 (comment) and manually remove previous release leads from the kubernetes-sig-leads group.

@alejandrox1 alejandrox1 changed the title Release Team Lead access for alejandrox1, daminisatya, and mrbobbytables Release Team Lead access for alejandrox1, mrbobbytables, and onlydole Jan 23, 2020
@alejandrox1
Copy link
Contributor Author

Adding @onlydole to the lead team (thank you very much for volunteering to help ❤️ )

@onlydole
Copy link
Member

Thank you for the opportunity of a lifetime! I’m looking forward to it 😄

@alejandrox1
Copy link
Contributor Author

@onlydole i'll start sending PRs to get you set up but meanwhile,can you please comment that you're aware of and agree to uphold the Security Release Process (see the first couple comments)

@onlydole
Copy link
Member

Absolutely!

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

/woof

@k8s-ci-robot
Copy link
Contributor

@onlydole: dog image

In response to this:

Absolutely!

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

/woof

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.

@justaugustus
Copy link
Member

Awesome! Welcome to the squad, @onlydole!

@alejandrox1 -- Please ensure that all update PRs add Taylor AND remove Damini where appropriate.

This was referenced Jan 24, 2020
Merged
Merged
Merged
@alejandrox1
Copy link
Contributor Author

Onboarding seems to be completed.

For the off boarding process I removed the previous RT lead and shadows as manager of the kubernetes-release-team mailing list.
Everything else is yet to be done @justaugustus

@justaugustus
Copy link
Member

@alejandrox1 -- Just a heads-up that the offboarding section is meant for your offboarding, not the previous Leads.

@alejandrox1
Copy link
Contributor Author

In that case this is all set i guess.
Should we close the issue or move it to the backlog?

@alejandrox1
Copy link
Contributor Author

Time to off-board me (mostly) 😿

@justaugustus
Copy link
Member

Offboarding for @alejandrox1 started here: kubernetes/org#1785

@justaugustus justaugustus mentioned this issue Apr 12, 2020
Merged
@justaugustus
Copy link
Member

justaugustus commented Apr 12, 2020 •
edited
Loading

Will be closed via kubernetes/k8s.io#742.
/close

@justaugustus
Copy link
Member

/close

@k8s-ci-robot
Copy link
Contributor

@justaugustus: Closing this issue.

In response to this:

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@justaugustus justaugustus

@alejandrox1 alejandrox1

Labels
area/release-eng Issues or PRs related to the Release Engineering subproject area/release-team Issues or PRs related to the release-team subproject lifecycle/frozen Indicates that an issue or PR should not be auto-closed due to staleness. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. sig/release Categorizes an issue or PR as relevant to SIG Release.
Projects
None yet
Milestone
v1.18
Development

No branches or pull requests
5 participants
@onlydole @justaugustus @mrbobbytables @alejandrox1 @k8s-ci-robot