From 60fb27e2b788b76ae4715f7785300c84299acf92 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 | 16 +++++++++------- 1 file changed, 9 insertions(+), 7 deletions(-) diff --git a/docs/release/release-tasks.md b/docs/release/release-tasks.md index b05a102d9ef7..8be42b194fd8 100644 --- a/docs/release/release-tasks.md +++ b/docs/release/release-tasks.md @@ -383,24 +383,26 @@ 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 -* ... +* Conference talks +* Github Issue (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 Team retrospective / pre-scheduled release cutting meetings -Stakeholders are: (TBD) +Stakeholders are: * End users of Cluster API * Contributors to core Cluster API * Provider implementers -* ... +* Downstream users (if applicable) #### Communicate beta to providers