From 65891845b7a52ccf5beeb7fe7320bf4ad4a2c471 Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Sat, 23 Aug 2025 13:25:00 +0200 Subject: [PATCH 1/6] Ansible 13 roadmap --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 81 +++++++++++++++++++ .../rst/roadmap/ansible_roadmap_index.rst | 1 + 2 files changed, 82 insertions(+) create mode 100644 docs/docsite/rst/roadmap/COLLECTIONS_13.rst diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst new file mode 100644 index 00000000000..8ebb4d4cb5a --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -0,0 +1,81 @@ +.. + THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! + For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. + For other changes, create a discussion as described in https://ansible.readthedocs.io/projects/ansible/devel/community/steering/community_topics_workflow.html#creating-a-topic + to discuss the changes. + (Creating a draft PR for this file and mentioning it in the community topic is also OK.) + +.. _ansible_13_roadmap: + +==================== +Ansible project 13.0 +==================== + +This release schedule includes dates for the `ansible `_ package, with a few dates for the `ansible-core `_ package as well. All dates are subject to change. See the `ansible-core 2.20 Roadmap `_ for the most recent updates on ``ansible-core``. + +.. contents:: + :local: + + +Release schedule +================= + +The schedule has been updated to match the :ref:`ansible-core 2.20 release schedule `. If that one gets modified again, the Ansible 12 pre-release and release dates will be shifted accordingly, and potentially more pre-releases will be inserted. + +:2025-09-15: ansible-core feature freeze. +:2025-09-22: Start of ansible-core 2.20 betas. +:2025-04-16: Ansible-13.0.0 alpha1; there will be more alpha releases usually following additional ansible-core 2.20 betas. +:2025-10-13: First ansible-core 2.20 release candidate. +:2025-10-14: Ansible-13.0.0 alphaX; there might be more alpha releases following additional ansible-core 2.19 release candidates. +:2025-11-03: Ansible-core-2.20.0 released. +:2025-11-03: Last day for collections to make backwards incompatible releases that will be accepted into Ansible-13. This includes adding new collections to Ansible 13.0.0; from now on new collections have to wait for 13.1.0 or later. +:2025-11-04: Ansible-13.0.0 beta1 -- feature freeze [2]_ (collection owners and interested users should test for bugs). +:2025-11-11: Ansible-13.0.0 rc1 [3]_ [4]_ (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release. +:2025-11-14: Last day to trigger an Ansible-13.0.0rc2 release because of major defects in Ansible-13.0.0rc1. +:2025-11-18: Ansible-13.0.0rc2 when necessary, otherwise Ansible-13.0.0 release. +:2025-11-25: Ansible-13.0.0 release when Ansible-13.0.0rc2 was necessary. +:2025-11-18 or 2025-11-25: Create the ansible-build-data directory and files for Ansible-14. +:2025-12-01: Release of ansible-core 2.20.1. +:2025-12-02: Release of Ansible-13.1.0 (bugfix + compatible features: every four weeks.) + +.. [2] 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-13.0.0 could ship with community.crypto 2.3.1. It would not ship with community.crypto 2.4.0. + +.. [3] After this date only changes blocking a release are accepted. Accepted changes require creating a new release candidate and may slip the final release date. + +.. [4] Collections will be updated to a new version only if a blocker is approved. Collection owners should discuss any blockers at a community meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `creating an Ansible Community Topic workflow `_. + +.. note:: + + Breaking changes will be introduced in Ansible 13.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 is 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 13 release collides with a pre-release of Ansible 14, the latter will be delayed. + If an Ansible 13 release collides with a stable Ansible 14 release, including 14.0.0, the Ansible 13 release will be delayed. + + +Ansible minor releases +======================= + +Ansible 13.x follows ansible-core-2.20.x releases, so releases will occur approximately every four weeks. If ansible-core delays a release for whatever reason, the next Ansible 13.x minor release will be delayed accordingly. + +Ansible 13.x minor releases may contain new features (including new collections) 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-13.0.0 ships with community.crypto 2.3.0, Ansible-13.1.0 could ship with community.crypto 2.4.0 but not community.crypto 3.0.0. + + +.. note:: + + Minor and patch releases will stop when Ansible-14 is released. See the :ref:`Release and Maintenance Page ` for more information. + +.. note:: + + We will not provide bugfixes or security fixes for collections that do not + provide updates for their major release cycle included in Ansible 13. + + +Communication +============= + +You can submit feedback on the current roadmap by creating a :ref:`community topic`. + +Visit the :ref:`Ansible communication guide` for details on how to join and use Ansible communication platforms. diff --git a/docs/docsite/rst/roadmap/ansible_roadmap_index.rst b/docs/docsite/rst/roadmap/ansible_roadmap_index.rst index b6a26272212..88e4d71822d 100644 --- a/docs/docsite/rst/roadmap/ansible_roadmap_index.rst +++ b/docs/docsite/rst/roadmap/ansible_roadmap_index.rst @@ -20,6 +20,7 @@ Visit the :ref:`Ansible communication guide` for details on how t :glob: :caption: Ansible Release Roadmaps + COLLECTIONS_13 COLLECTIONS_12 COLLECTIONS_11 COLLECTIONS_10 From 21cdbbd227f56684f3423dd6a979cfe24801a114 Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Sun, 24 Aug 2025 13:38:44 +0200 Subject: [PATCH 2/6] Apply suggestions from code review Co-authored-by: Felix Fontein --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst index 8ebb4d4cb5a..74140d8c03f 100644 --- a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -24,7 +24,7 @@ The schedule has been updated to match the :ref:`ansible-core 2.20 release sched :2025-09-15: ansible-core feature freeze. :2025-09-22: Start of ansible-core 2.20 betas. -:2025-04-16: Ansible-13.0.0 alpha1; there will be more alpha releases usually following additional ansible-core 2.20 betas. +:2025-09-17: Ansible-13.0.0 alpha1; there will be more alpha releases usually following additional ansible-core 2.20 betas. :2025-10-13: First ansible-core 2.20 release candidate. :2025-10-14: Ansible-13.0.0 alphaX; there might be more alpha releases following additional ansible-core 2.19 release candidates. :2025-11-03: Ansible-core-2.20.0 released. @@ -38,7 +38,7 @@ The schedule has been updated to match the :ref:`ansible-core 2.20 release sched :2025-12-01: Release of ansible-core 2.20.1. :2025-12-02: Release of Ansible-13.1.0 (bugfix + compatible features: every four weeks.) -.. [2] 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-13.0.0 could ship with community.crypto 2.3.1. It would not ship with community.crypto 2.4.0. +.. [2] 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 3.3.0; Ansible-13.0.0 could ship with community.crypto 3.3.1. It would not ship with community.crypto 3.4.0. .. [3] After this date only changes blocking a release are accepted. Accepted changes require creating a new release candidate and may slip the final release date. @@ -58,9 +58,9 @@ The schedule has been updated to match the :ref:`ansible-core 2.20 release sched Ansible minor releases ======================= -Ansible 13.x follows ansible-core-2.20.x releases, so releases will occur approximately every four weeks. If ansible-core delays a release for whatever reason, the next Ansible 13.x minor release will be delayed accordingly. +Ansible 13.x follows ansible-core-2.20.x releases, so releases will occur approximately every four weeks. If ansible-core delays a release for whatever reason, the next Ansible 13.x minor release will usually (but not always) be delayed accordingly. -Ansible 13.x minor releases may contain new features (including new collections) 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-13.0.0 ships with community.crypto 2.3.0, Ansible-13.1.0 could ship with community.crypto 2.4.0 but not community.crypto 3.0.0. +Ansible 13.x minor releases may contain new features (including new collections) 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-13.0.0 ships with community.crypto 3.3.0, Ansible-13.1.0 could ship with community.crypto 3.4.0 but not community.crypto 4.0.0. .. note:: From 72686300787b7ad598ad74c3e7a1bc583db5b06f Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Sun, 24 Aug 2025 17:39:04 +0200 Subject: [PATCH 3/6] Update docs/docsite/rst/roadmap/COLLECTIONS_13.rst Co-authored-by: Felix Fontein --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst index 74140d8c03f..02fe73c181b 100644 --- a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -24,7 +24,7 @@ The schedule has been updated to match the :ref:`ansible-core 2.20 release sched :2025-09-15: ansible-core feature freeze. :2025-09-22: Start of ansible-core 2.20 betas. -:2025-09-17: Ansible-13.0.0 alpha1; there will be more alpha releases usually following additional ansible-core 2.20 betas. +:2025-09-23: Ansible-13.0.0 alpha1; there will be more alpha releases usually following additional ansible-core 2.20 betas. :2025-10-13: First ansible-core 2.20 release candidate. :2025-10-14: Ansible-13.0.0 alphaX; there might be more alpha releases following additional ansible-core 2.19 release candidates. :2025-11-03: Ansible-core-2.20.0 released. From 3233f720575dc0691ed48f449e2a7c0796cc5c7f Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Wed, 10 Sep 2025 08:55:19 +0200 Subject: [PATCH 4/6] Commit review suggestion from felixfontein Co-authored-by: Felix Fontein --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst index 02fe73c181b..e9e28809c1b 100644 --- a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -42,7 +42,7 @@ The schedule has been updated to match the :ref:`ansible-core 2.20 release sched .. [3] After this date only changes blocking a release are accepted. Accepted changes require creating a new release candidate and may slip the final release date. -.. [4] Collections will be updated to a new version only if a blocker is approved. Collection owners should discuss any blockers at a community meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `creating an Ansible Community Topic workflow `_. +.. [4] Collections will be updated to a new version only if a blocker is approved. Collection owners should discuss any blockers at a community meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the :ref:`creating an Ansible Community Topic workflow `. .. note:: From c1aa1436f35fe963c4613b8b09ba27cfa80fdecd Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Wed, 10 Sep 2025 17:21:24 +0200 Subject: [PATCH 5/6] Link ansible-core roadmap using RST label --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst index e9e28809c1b..b47cf340171 100644 --- a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -11,7 +11,7 @@ Ansible project 13.0 ==================== -This release schedule includes dates for the `ansible `_ package, with a few dates for the `ansible-core `_ package as well. All dates are subject to change. See the `ansible-core 2.20 Roadmap `_ for the most recent updates on ``ansible-core``. +This release schedule includes dates for the `ansible `_ package, with a few dates for the `ansible-core `_ package as well. All dates are subject to change. See the :ref:`ansible-core 2.20 Roadmap ` for the most recent updates on ``ansible-core``. .. contents:: :local: From 2b95dbf85462c3e314d91afe759e980d10a22bce Mon Sep 17 00:00:00 2001 From: Mario Lenz Date: Wed, 10 Sep 2025 17:34:54 +0200 Subject: [PATCH 6/6] Undo last ansible.readthedocs.io link --- docs/docsite/rst/roadmap/COLLECTIONS_13.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst index b47cf340171..7170c85dcf2 100644 --- a/docs/docsite/rst/roadmap/COLLECTIONS_13.rst +++ b/docs/docsite/rst/roadmap/COLLECTIONS_13.rst @@ -1,7 +1,7 @@ .. THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. - For other changes, create a discussion as described in https://ansible.readthedocs.io/projects/ansible/devel/community/steering/community_topics_workflow.html#creating-a-topic + For other changes, create a discussion as described in https://docs.ansible.com/ansible/devel/community/steering/community_topics_workflow.html#creating-a-topic to discuss the changes. (Creating a draft PR for this file and mentioning it in the community topic is also OK.)