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.

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

Release Team: Add Release Team members onboarding documentation #9274

Closed
furkatgofurov7 opened this issue Aug 22, 2023 · 7 comments · Fixed by #9565
Closed

Release Team: Add Release Team members onboarding documentation #9274

furkatgofurov7 opened this issue Aug 22, 2023 · 7 comments · Fixed by #9565
Assignees
Labels
area/release Issues or PRs related to releasing kind/documentation Categorizes issue or PR as related to documentation. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@furkatgofurov7
Copy link
Member

What would you like to be added (User Story)?

At the beginning of the release cycle, the release team members should review the documentation to become aware of the existing processes and tools used throughout the cycle.

Detailed Description

The idea is to have onboarding documentation per sub-team (CI signal, Comms) which outlines the tools/processes used by each team in high level. For example, CI team members should be aware/familiarize themselves with:

  • prow, how to use prow commands, interact with prow etc
  • testgrid dashboard, what jobs are relevant
  • test-infra repo where all the CI jobs setup live
  • k8s triage

Comms team:

  • release note generation tool
  • important communication channels
  • ...

** Additionally, we could document in each sub-team Leads and Release Lead tasks about conducting an onboarding session with shadows in the first week of the release cycle to go over general responsibilities and expectations.

Anything else you would like to add?

No response

Label(s) to be applied

/kind documentation
/area release

Tracked in: #9104

@k8s-ci-robot k8s-ci-robot added kind/documentation Categorizes issue or PR as related to documentation. area/release Issues or PRs related to releasing needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Aug 22, 2023
@furkatgofurov7
Copy link
Member Author

furkatgofurov7 commented Aug 22, 2023

@kubernetes-sigs/cluster-api-release-team
cc @killianmuldoon @CecileRobertMichon @sbueringer

@furkatgofurov7
Copy link
Member Author

/assign

@furkatgofurov7
Copy link
Member Author

/cc @fabriziopandini

@sbueringer
Copy link
Member

Sounds good

@g-gaston
Copy link
Contributor

Sounds good, the more we can write down the more time we save in future cycles and the less meetings we'll need.

@fabriziopandini
Copy link
Member

/triage accepted
+1, I see this like another iteration of our documentation about release team/process

@k8s-ci-robot k8s-ci-robot added triage/accepted Indicates an issue or PR is ready to be actively worked on. and removed needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Sep 6, 2023
@furkatgofurov7
Copy link
Member Author

Thanks for inputs folks, I'll open a PR to add the notes shortly

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/release Issues or PRs related to releasing kind/documentation Categorizes issue or PR as related to documentation. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
Development

Successfully merging a pull request may close this issue.

5 participants