Sig-release: Ensure all release team handbooks include an item for holding an initial team meeting with their shadows

[karenhchu]

We need to add to the release team lead handbook a note holding an initial team meeting with their shadows in order to introduce everyone, their collective tasks, and upcoming timeline. This will better foster a team atmosphere and allow members to help/cover for each other accordingly.

[justaugustus]

Great idea, @karenhchu!
I think this should be listed in every handbook.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[palnabarun]

/remove-lifecycle stale

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[LappleApple]

In our release team process-improvement prioritisation sessions a few folks mentioned taking a closer look at the general RT onboarding process and make some adjustments. Maybe we can try to do that broader review of onboarding, create an initiative for it, and include this item as a to-do of that initiative?

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[onlydole]

/remove-lifecycle rotten

[karenhchu]

Sure thing. Should I leave this open or close it since it'll be addressed in newer efforts @LappleApple?

[lauriapple2]

Hey @karenhchu: I'd say let's leave it open for a bit longer, because this week I am going to work a bit on organizing our thoughts on onboarding and driving inclusivity.

[hasheddan]

/assign

[palnabarun]

Based on the above discussions and discussions over the Release Team meetings, I have retitled the issue to mention the latest status quo.

Also, putting out a checklist for each team handbook.

• [x] Bug Triage
• [x] CI Signal
• [x] Communications
• [x] Docs
• [x] Enhancements
• [x] Release Notes

PS: This is a nice task to be done by the shadows of each team.

cc: @kubernetes/release-team

/assign

[palnabarun]

Enhancements Handbook would be updated through https://github.com/kubernetes/sig-release/pull/1304/commits/df174e62dace7c7fbb5e64dc8647c90539c182f8#diff-c853db51181791969e437e9f720a7ef21fbcf460f1eebda80b8ae6a7e2673ba8R96 :)

[annajung]

Docs handbook already has a section to do this and can be marked off as completed
https://github.com/kubernetes/sig-release/blob/master/release-team/role-handbooks/docs/Release-Timeline.md#meet-with-shadows

[palnabarun]

Thank you @annajung for the update. 😃

[LappleApple]

/sig release
/area release-team
/kind documentation

[jeremyrickard]

Bug Triage updated in https://github.com/kubernetes/sig-release/pull/1345

[jeremyrickard]

ANNNND comms is updated ☝️ . Going to close this issue now!

[jeremyrickard]

/close

Thanks for the updates, everyone!

[k8s-ci-robot]

@jeremyrickard: Closing this issue.

In response to this:

/close

Thanks for the updates, everyone!

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.