Skip to content

Commit

Permalink
Address comments from comms team lead
Browse files Browse the repository at this point in the history
Signed-off-by: Furkat Gofurov <[email protected]>
  • Loading branch information
furkatgofurov7 committed Oct 18, 2023
1 parent 64c852c commit ef2982f
Showing 1 changed file with 3 additions and 1 deletion.
4 changes: 3 additions & 1 deletion docs/release/release-team-onboarding.md
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,9 @@ Now, let's dive into the specific onboarding notes for each sub-team below.
### Comms Lead Shadows Team

- Understand Release Process:
- Familiarize yourself with project's release process and the [tool](https://github.com/kubernetes-sigs/cluster-api/tree/main/hack/tools/release) used for generating release notes.
- Get to know how project's release process works.
- Walk through the [release note generation process](../release/release-tasks.md#create-pr-for-release-notes) and try to generate notes by yourself. This is the most important process the comms team is in charge of.
- Familiarize yourself with the release notes tool [code](https://github.com/kubernetes-sigs/cluster-api/tree/main/hack/tools/release). You'll probably need to update this code during the release cycle to cover new cases or add new features.
- Documentation familiarity:
- Explore project's documentation and start learning how to update and maintain it.
- Communication channels:
Expand Down

0 comments on commit ef2982f

Please sign in to comment.