Add a note checking with the maintainers about comms emails

docs/release/release-tasks.md

@@ -82,9 +82,10 @@ As of now we ask for volunteers in Slack and office hours.
 
 #### Finalize release schedule and team
 
-1. Finalize release schedule and team in `release-1.4.md`.
+1. Finalize release schedule and team in `release-x.y.md`.
 2. Update 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
 
@@ -367,6 +368,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: Ensure that the communication email was received by the community. If unsure, check with the maintainers if the email was pending for approval and needs to be unblocked.
 * Slack
 * Office hours
 * Cluster API book