From 69fa1b0d17294634ddab3ff02e5de7e256aded10 Mon Sep 17 00:00:00 2001 From: Furkat Gofurov Date: Fri, 20 Oct 2023 21:05:10 +0300 Subject: [PATCH] Define details of "Communicate key dates to the community" in release tasks doc Signed-off-by: Furkat Gofurov --- docs/release/release-tasks.md | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/docs/release/release-tasks.md b/docs/release/release-tasks.md index b05a102d9ef7..c8fcb82f6ad4 100644 --- a/docs/release/release-tasks.md +++ b/docs/release/release-tasks.md @@ -383,24 +383,24 @@ 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 +* #cluster-api Slack channel * Office hours +* Release Team meetings * Cluster API book -* ... +* [Github Issue](https://github.com/kubernetes-sigs/cluster-api/blob/main/docs/release/release-tasks.md#communicate-beta-to-providers) (when communicating beta release to providers) -Relevant information includes: (TBD) +Relevant information includes: -* Beta, RC, GA release +* Beta, RC, GA and patch release * Start of code freeze * Implementation progress -* ... +* Release delays and changes if applicable -Stakeholders are: (TBD) +Stakeholders are: * End users of Cluster API * Contributors to core Cluster API * Provider implementers -* ... #### Communicate beta to providers