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

📖 add a note to check with maintainers for blocked comms emails #8819

Merged
merged 1 commit into from
Jul 22, 2023
Merged

📖 add a note to check with maintainers for blocked comms emails #8819

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/release/release-tasks.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,6 +89,7 @@ As of now we ask for volunteers in Slack and office hours.
1. Finalize release schedule and team in the [docs/release/releases](../../docs/release/releases), e.g. [release-1.4.md](../../docs/release/releases/release-1.4.md).
2. Update @cluster-api-release-team Slack user group and GitHub team accordingly.
<br>Prior art: https://github.com/kubernetes-sigs/cluster-api/issues/7476
3. Announce the _release team_ and _release schedule_ to the mailing list.

#### Prepare main branch for development of the new release

Expand Down Expand Up @@ -346,6 +347,7 @@ upcoming code freezes etc based on the [release timeline (1.4 example)](./releas

Information can be distributed via:
* `sig-cluster-lifecycle` mailing list
* Note: The person sending out the email should ensure that they are first part of the mailing list. If the email is sent out is not received by the community, reach out to the maintainers to unblock and approve the email.
* Slack
* Office hours
* Cluster API book
Expand Down