Define details of "Communicate key dates to the community" in release…

… tasks doc

Signed-off-by: Furkat Gofurov <furkat.gofurov@suse.com>

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