Sig-release: Assemble Kubernetes 1.14 Release Team

Created on 15 Nov 2018  ยท  97Comments  ยท  Source: kubernetes/sig-release

This is the official issue for assembling the Kubernetes 1.14 Release Team.

Please review the Release Team Selection docs for details on the process and criteria.

We are currently in discussions around improving / refining the selection process (https://github.com/kubernetes/sig-release/issues/368, https://github.com/kubernetes/sig-release/issues/369), but would like to open this issue to get the ball rolling.

/sig release
cc: @AishSundar @spiffxp @calebamiles @tpepper @jdumars

sirelease

Most helpful comment

It's really wonderful to see all of the people who have volunteered for the 1.14 Release Team!

I've seen your emails, DMs, and notes here; just churning through the post-holiday backlog.

The questionnaire for Release Team shadows will be out next week. Anyone still interested in shadowing will be required to submit it to be considered for a position. I'll post it here and on k-dev, once it's ready to go. :)

All 97 comments

/assign @justaugustus @AishSundar @spiffxp

So far, the following people have reached out to me to participate:

  • @d-nishi - CI Signal shadow
  • @nikhita - Patch Release Management Team
  • @yue9944882 - Patch Release Management Team
  • @lledru - ~Bug Triage~ Enhancements shadow

I'd like to volunteer for Release Notes shadow! :)

I'd like to join the Patch Release Team.

Since I'm the Branch Manager Shadow in 1.12 and 1.13, I can continue to work with branch management if needed.

Hey everyone! :wave: I'd love to join the 1.14 release team!

So far seeing by roles, if there is free space, I would love to be shadow for Patch Release or Branch Manager.

I'd like to nominate @dstrebel to be the 1.14 Release Notes Lead!

I'd like to shadow bug triage again or CI signal!
EDIT: Spoke to @nikopen & since 1.13 was a short release, I'd like to continue as bug triage shadow :)

I'd like to shadow someone

Iโ€™d like to shadow on the communications team

I would like to shadow the patch release management

I would like to officially nominate @spiffxp as the 1.14 Release lead :) Go SIG-Beard !!!

SIG BEARD 4EVR!
/meow space

I would like to nominate @claurence as Enhancements Lead for 1.14. I will take a step back into a shadow/mentor role for 1.14 and take the opportunity to update some of the Enhancement Lead timetables/processes.

@justaugustus: Bad category. Please see https://api.thecatapi.com/api/categories/list

In response to this:

SIG BEARD 4EVR!
/meow space

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.

I would like to nominate @lachie83 for branch manager shadow or patch release shadow.

(hmm, space cats are broken, but I still want to see a kitteh...)
/meow

@justaugustus: https://thecatapi.com appears to be down

In response to this:

(hmm, space cats are broken, but I still want to see a kitteh...)
/meow

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.

/meowvie space

@xmudrii: Bad category. Please see https://api.thecatapi.com/api/categories/list

In response to this:

/meowvie space

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.

If there's more needed/space, I'd like to volunteer as a patch release shadow too ๐Ÿ˜„

I would like to shadow for CI signal team if there is still space :))

I'd love to shadow the Bug Triage or Communications team

Have listened to the speech for your team during KubeCon Shanghai. I am so interested to be part in the patch release team. Currently I'm on the chinese i18n translation team, doc team would work for me as well. Also, the ReadMe.md for doc team is missing @justaugustus.

I would like to stay as Enhancements Shadow for this milestone.

cc @smourapina

I would like to nominate @hoegaarden for Branch Manager lead.

And also second @idealhack for Patch Release Manager shadow.

I would like to nominate @lachie83 for branch manager shadow or patch release shadow.

@dstrebel Thanks. I accept your nomination.

I'd like to nominate the fantastic @jimangel for the Docs lead

I second the nomination of @lledru as enhancements shadow, been working with him on daily basis, he will be a great addition to the team.

i'd like to be part of (or shadow) the release team

Thank you @idealhack for bring this to my attention!
I just got back from KubeCon China and I am very interested in volunteering as a shadow. I have a preference for CI Signal or Branch Manager (if possible).

@AishSundar Thank you

I am super happy to fulfil the role for the release branch management lead, if everybody is happy with this being done from EMEA timezones.
Thanks @dougm for the nomination!

I had like to continue the test-infra shadow. :-)

First set of leads have been added in this PR: https://github.com/kubernetes/sig-release/pull/377
Once we place the leads, I'll move on to adding the shadows.

Thank you soooooooo much to everyone who has volunteered thus far. Let's keep the volunteers coming! :)

I would like to shadow for Test Infra team. Thanks.

I'd like to nominate Natasha Woods (nwoods) for Communications Lead! I would also be happy to shadow and help out.

@kbarnard10 Wrong nwoods :-)

Having shadowed for 1.12 and 1.13, I'd be willing to give a shot for test-infra lead.

We really need a shadow for @spiffxp as release lead...are there past role leads (or shadows?) who are interested in doing this for 1.13?

@kubernetes/sig-release -- anyone interested in stepping up as 1.14 Release Team Lead Shadow?

I nominate @mariantalla as CI Signal Lead for 1.14.

@justaugustus I'd shadow @spiffxp

Tagging @nwoods3 for Communications Lead:

I'd like to nominate Natasha Woods (nwoods) for Communications Lead! I would also be happy to shadow and help out.

@BenTheElder thanks for volunteering to shadow Release Team Lead!
@spiffxp -- do you accept?

I would love to reprise my role as Communications Lead for 1.14. Thank you for the nomination @kbarnard10 :)

Happy to continue as Bug Triage Lead for 1.14 as discussed in Release meeting :>

+1 (non-binding) on @nwoods3's nomination :)

I would love to shadow Docs or Release Notes. Thanks!

I will like to shadow for release notes or Docs

@BenTheElder thanks for volunteering to shadow Release Team Lead!
@spiffxp -- do you accept?

Chatted with Ben offline. I do, but I am also interested in finding another (non-Google) shadow.

I'd like to shadow communications again if possible!

I'd like to shadow for Test Infra team or Patch Release Management Team

I'd like to shadow Patch Release Management Team

I'd like to shadow CI Signal again

I would like to shadow for CI Signal.

cc @onyiny-ang

I would like to shadow for docs, release notes, test infra, or release team lead

Iโ€™d like to shadow test-infra! ๐Ÿ˜Š๐Ÿ˜…

I would like to shadow test-infra! ๐Ÿ˜„

I'd like to shadow for either Test Infra, CI Signal (or Enhancements if both are already not available).

@justaugustus I would like to shadow for this release if possible (based on our talk)

To confirm @ameukam's cc, I volunteer to shadow release-notes again for this release. I think it would be great if we could explore some ways to automate verb tense consistency/formatting checks as per @marpaia's lightening talk at Kubecon. It might also be beneficial to re-evaluate the current organization of release-notes and develop some best practices around how release-notes should be organized (if it's determined that the current organization could be improved). For example, coordinating with sig-leads communications and docs lead and shadows prior to the release to identify overarching themes or major/important features and making sure they have high visibility within the release notes to ensure consistency so it's easier for users to digest and distinguish defining features of each release. I guess that's my platform :joy:

There's been a few volunteers above already, but I'd like to volunteer for test-infra shadow as well ๐Ÿ˜„

I would love to shadow the Docs again.

I have never contributed to Kubernetes, but active in OpenStack community, But love to shadow on test-infra stuff.

Can volunteer as shadow for docs or test-infra. Or volunteer otherwise if spots are full.

Hey everyone! ๐Ÿ‘‹ I would love to contribute anywhere I can.. I'd love to passively participate this time as I haven't done this before. I'd like to play the shadow role anywhere ๐Ÿ™‚

I would love to shadow test-infra, docs, or CI signal if possible. Are there any prerequisites to do so?

I would like to shadow for test-infra or docs. Or anywhere where help is wanted

Iโ€™m here to serve ๐Ÿ˜Š

I'd like to shadow for either Enhancements or Test Infra. It would a good dive for me to the Kubernetes community!

@jaredbhatti and I would like to shadow docs to prepare for the following release

Thanks for all the interest y'all. The Handbooks for each of the roles can be found @ https://github.com/kubernetes/sig-release/tree/master/release-team/role-handbooks. Please read them to familiarize yourself with the role and an overview of the work involved.

I know I might be a bit late for this release, but I'd like to shadow for the Patch Release Management Team or the Bug Triage if possible.

I would love to shadow docs or communications.

I'd love to shadow docs again :)

I too would like to shadow docs.

On Tue, Dec 18, 2018, 10:43 AM Naomi Pentrel <[email protected]
wrote:

I'd love to shadow docs again :)

โ€”
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/sig-release/issues/372#issuecomment-448325963,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AF3Lghn1S5X7RJuOzDphZS-5uwv3WT4Wks5u6Tc7gaJpZM4Yg6Tu
.

I know there have been a lot of requests for it, but I would like to shadow CI Signal under @mariantalla as well while doing anything needed for Enhancements assistance. I can take a far back seat to let others have the chance. I would like to familiarize myself with more aspects of the release process.

Hello I would like to shadow Communications/Docs/Release Notes

I like to shadow test-infra

I would like for us to aim to have the team locked in place by the end of next week (Friday, Jan 11th)

If there is any room for me anywhere to help/shadow, I would love to be in

I would like to shadow bug triage or comms if possible.

It's really wonderful to see all of the people who have volunteered for the 1.14 Release Team!

I've seen your emails, DMs, and notes here; just churning through the post-holiday backlog.

The questionnaire for Release Team shadows will be out next week. Anyone still interested in shadowing will be required to submit it to be considered for a position. I'll post it here and on k-dev, once it's ready to go. :)

@justaugustus i would like to shadow on patch release management, bug triage and enhancements. Any one is good :-)

@justaugustus when do we know what we got ? Should we attend the next sig-release ?

The questionnaire for Release Team shadows will be out next week. Anyone still interested in shadowing will be required to submit it to be considered for a position. I'll post it here and on k-dev, once it's ready to go. :)

@krmayankk -- the survey will be out tomorrow. Hang tight in the meantime.

The Kubernetes 1.14 Release Team shadow questionnaire is live!
If you're interested in participating in the 1.14 Release Team, please fill it out: https://www.surveymonkey.com/r/k8s-114-rt-shadows

Given that we just got the questionnaire out yesterday, doesn't seem realistic to lock in place today. Let's aim to have the team locked in place by the end of next week (Friday, Jan 18th)

@spiffxp -- SGTM!

Did the Kubernetes 1.14 Release Team shadows already form based on the questionnaire?

@markyjackson-taulia -- the 1.14 Leads are working through the survey results. You should have a response this week.

/close
I think our team has been pretty well assembled by this point

@spiffxp: Closing this issue.

In response to this:

/close
I think our team has been pretty well assembled by this point

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.

It seems we don't have a patch release team yet.

Was this page helpful?
0 / 5 - 0 ratings