Clarify that two releases will happen on two separate days, and clari…

…fy which one will happen first (ansible#39) * Clarify that two releases will happen on two separate days, and clarify which one will happen first. * Add note on general discretion. * Rewrite according to review comments. * Add comma. Co-authored-by: Maxwell G <[email protected]>
gotmax23 · Jul 5, 2023 · 460f9e9 · 460f9e9
1 parent 1a1aa0b
commit 460f9e9
Show file tree

Hide file tree

Showing 2 changed files with 12 additions and 0 deletions.
diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_8.rst b/docs/docsite/rst/roadmap/COLLECTIONS_8.rst
@@ -40,6 +40,12 @@ Release schedule
 
   Breaking changes will be introduced in Ansible 8.0.0, although we encourage the use of deprecation periods that will show up in at least one Ansible release before the breaking change happens, this is not guaranteed.
 
+.. note::
+
+  In general, it's in the discretion of the release manager to delay a release by 1-2 days for reasons such as personal (schedule) problems, technical problems (CI/infrastructure breakdown), and so on.
+  However, in case two releases are planned for the same day, a release of the latest stable version takes precedence. This means that if a stable Ansible 8 release collides with a pre-release of Ansible 9, the latter will be delayed.
+  If a Ansible 8 release collides with a stable Ansible 9 release, including 9.0.0, the Ansible 8 release will be delayed.
+
 
 Ansible minor releases
 =======================

diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_9.rst b/docs/docsite/rst/roadmap/COLLECTIONS_9.rst
@@ -40,6 +40,12 @@ Release schedule
 
   Breaking changes will be introduced in Ansible 9.0.0. We encourage the use of deprecation periods that give advance notice of breaking changes at least one Ansible release before they are introduced. However, deprecation notices are not guaranteed to take place.
 
+.. note::
+
+  In general, it's in the discretion of the release manager to delay a release by 1-2 days for reasons such as personal (schedule) problems, technical problems (CI/infrastructure breakdown), and so on.
+  However, in case two releases are planned for the same day, a release of the latest stable version takes precedence. This means that if a stable Ansible 9 release collides with a pre-release of Ansible 10, the latter will be delayed.
+  If a Ansible 9 release collides with a stable Ansible 10 release, including 10.0.0, the Ansible 9 release will be delayed.
+
 
 Planned major changes
 =====================