From 059dc69842f9a604e975a122be18112880ad9c6b Mon Sep 17 00:00:00 2001 From: Nawaz Hussain K Date: Wed, 7 Jun 2023 13:03:11 -0700 Subject: [PATCH] Add a note checking with the maintainers about comms emails --- docs/release/release-tasks.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/release/release-tasks.md b/docs/release/release-tasks.md index b40d0626c428..b3f0a30679f8 100644 --- a/docs/release/release-tasks.md +++ b/docs/release/release-tasks.md @@ -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.
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 @@ -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