Update Ansible 7 roadmap (#79307) (#79311)

(cherry picked from commit 852e2d7550)

Co-authored-by: Mario Lenz <m@riolenz.de>

docs/docsite/rst/roadmap/COLLECTIONS_7.rst

@@ -26,9 +26,11 @@ Release schedule
 :2022-11-08: Create the ansible-build-data directory and files for Ansible-8.
 :2022-11-08: Ansible-7.0.0 beta1 -- feature freeze [1]_ (weekly beta releases; collection owners and interested users should test for bugs).
 :2022-11-15: Ansible-7.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed; test and alert us to any blocker bugs).  Blocker bugs will slip release.
-:2022-11-29: Ansible-7.0.0 release.
-:2022-12-06: Release of ansible-core 2.14.1.
-:2022-12-20: Release of Ansible-7.1.0 (bugfix + compatible features: every three weeks.)
+:2022-11-18: Last day to trigger an Ansible-7.0.0rc2 release because of major defects in Ansible-7.0.0rc1.
+:2022-11-22: Ansible-7.0.0rc2 when necessary, otherwise Ansible-7.0.0 release.
+:2022-11-29: Ansible-7.0.0 release when Ansible-7.0.0rc2 was necessary.
+:2022-12-05: Release of ansible-core 2.14.1.
+:2022-12-06: Release of Ansible-7.1.0 (bugfix + compatible features: every four weeks.)
 
 .. [1] No new modules or major features accepted after this date. In practice, this means we will freeze the semver collection versions to compatible release versions. For example, if the version of community.crypto on this date was community.crypto 2.3.0; Ansible-7.0.0 could ship with community.crypto 2.3.1.  It would not ship with community.crypto 2.4.0.
 
@@ -44,7 +46,7 @@ Release schedule
 Ansible minor releases
 =======================
 
-Ansible 7.x minor releases will occur approximately every three weeks if changes to collections have been made or if it is deemed necessary to force an upgrade to a later ansible-core-2.14.x.  Ansible 7.x minor releases may contain new features but not backwards incompatibilities.  In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-7.0.0 ships with community.crypto 2.3.0; Ansible-6.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0.
+Ansible 7.x minor releases will occur approximately every four weeks if changes to collections have been made or to align to a later ansible-core-2.14.x.  Ansible 7.x minor releases may contain new features but not backwards incompatibilities.  In practice, this means we will include new collection versions where either the patch or the minor version number has changed but not when the major number has changed. For example, if Ansible-7.0.0 ships with community.crypto 2.3.0; Ansible-6.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0.
 
 
 .. note::