|
| 1 | +.. |
| 2 | + THIS DOCUMENT IS OWNED BY THE ANSIBLE COMMUNITY STEERING COMMITTEE. ALL CHANGES MUST BE APPROVED BY THE STEERING COMMITTEE! |
| 3 | + For small changes (fixing typos, language errors, etc.) create a PR and ping @ansible/steering-committee. |
| 4 | + For other changes, create a discussion as described in https://docs.ansible.com/ansible/devel/community/steering/community_topics_workflow.html#creating-a-topic |
| 5 | + to discuss the changes. |
| 6 | + (Creating a draft PR for this file and mentioning it in the community topic is also OK.) |
| 7 | +
|
| 8 | +.. _ansible_12_roadmap: |
| 9 | + |
| 10 | +==================== |
| 11 | +Ansible project 12.0 |
| 12 | +==================== |
| 13 | + |
| 14 | +This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-core <https://pypi.org/project/ansible-core/>`_ package as well. All dates are subject to change. See the `ansible-core 2.19 Roadmap <https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_19.html>`_ for the most recent updates on ``ansible-core``. |
| 15 | + |
| 16 | +.. contents:: |
| 17 | + :local: |
| 18 | + |
| 19 | + |
| 20 | +Release schedule |
| 21 | +================= |
| 22 | + |
| 23 | + |
| 24 | +:2025-03-31: ansible-core feature freeze, stable-2.19 branch created. |
| 25 | +:2025-04-07: Start of ansible-core 2.19 betas |
| 26 | +:2025-04-08: Ansible-12.0.0 alpha1 [1]_ |
| 27 | +:2025-04-28: First ansible-core 2.19 release candidate. |
| 28 | +:2025-04-29: Ansible-12.0.0 alpha2 [1]_ |
| 29 | +:2025-05-19: Ansible-core-2.19.0 released. |
| 30 | +:2025-05-19: Last day for collections to make backwards incompatible releases that will be accepted into Ansible-12. This includes adding new collections to Ansible 12.0.0; from now on new collections have to wait for 12.1.0 or later. |
| 31 | +:2025-05-20: Ansible-12.0.0 beta1 -- feature freeze [2]_ (collection owners and interested users should test for bugs). |
| 32 | +:2025-05-27: Ansible-12.0.0 rc1 [3]_ [4]_ (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release. |
| 33 | +:2025-05-30: Last day to trigger an Ansible-12.0.0rc2 release because of major defects in Ansible-12.0.0rc1. |
| 34 | +:2025-06-03: Ansible-12.0.0rc2 when necessary, otherwise Ansible-12.0.0 release. |
| 35 | +:2025-06-10: Ansible-12.0.0 release when Ansible-12.0.0rc2 was necessary. |
| 36 | +:2025-06-03 or 2023-06-10: Create the ansible-build-data directory and files for Ansible-13. |
| 37 | +:2025-06-16: Release of ansible-core 2.19.1. |
| 38 | +:2025-06-17: Release of Ansible-12.1.0 (bugfix + compatible features: every four weeks.) |
| 39 | + |
| 40 | +.. [1] In case there are any additional ansible-core beta releases or release candidates, we will try to do another Ansible-12.0.0 alpha release. This might mean that we will release Ansible-12.0.0 alpha2 earlier (and release Ansible-12.0.0 alpha3 or later on 2025-04-29) and / or release one or more additional alpha after 2024-04-29. |
| 41 | +
|
| 42 | +.. [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-12.0.0 could ship with community.crypto 2.3.1. It would not ship with community.crypto 2.4.0. |
| 43 | +
|
| 44 | +.. [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. |
| 45 | +
|
| 46 | +.. [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 <https://docs.ansible.com/ansible/devel/community/steering/community_topics_workflow.html#creating-a-topic>`_. |
| 47 | +
|
| 48 | +.. note:: |
| 49 | + |
| 50 | + Breaking changes will be introduced in Ansible 12.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. |
| 51 | + |
| 52 | +.. note:: |
| 53 | + |
| 54 | + 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. |
| 55 | + 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 12 release collides with a pre-release of Ansible 13, the latter will be delayed. |
| 56 | + If an Ansible 12 release collides with a stable Ansible 13 release, including 13.0.0, the Ansible 12 release will be delayed. |
| 57 | + |
| 58 | + |
| 59 | +Planned major changes |
| 60 | +===================== |
| 61 | + |
| 62 | +- The inspur.sm collection will be removed as it is unmaintained (https://github.com/ansible-community/ansible-build-data/issues/424). |
| 63 | +- The netapp.storagegrid collection will be removed as it is unmaintained (https://github.com/ansible-community/ansible-build-data/issues/434). |
| 64 | +- The frr.frr collection will be removed as it is unmaintained (https://github.com/ansible-community/ansible-build-data/issues/437). |
| 65 | +- The openvswitch.openvswitch collection will be removed as it is unmaintained (https://github.com/ansible-community/ansible-build-data/issues/437). |
| 66 | + |
| 67 | +You can install removed collections manually with ``ansible-galaxy collection install <collection_name>``. |
| 68 | + |
| 69 | + |
| 70 | +Ansible minor releases |
| 71 | +======================= |
| 72 | + |
| 73 | +Ansible 12.x follows ansible-core-2.19.x releases, so releases will occur approximately every four weeks. If ansible-core delays a release for whatever reason, the next Ansible 12.x minor release will be delayed accordingly. |
| 74 | + |
| 75 | +Ansible 12.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-12.0.0 ships with community.crypto 2.3.0, Ansible-12.1.0 could ship with community.crypto 2.4.0 but not community.crypto 3.0.0. |
| 76 | + |
| 77 | + |
| 78 | +.. note:: |
| 79 | + |
| 80 | + Minor and patch releases will stop when Ansible-13 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. |
| 81 | + |
| 82 | +.. note:: |
| 83 | + |
| 84 | + We will not provide bugfixes or security fixes for collections that do not |
| 85 | + provide updates for their major release cycle included in Ansible 12. |
| 86 | + |
| 87 | +Communication |
| 88 | +============= |
| 89 | + |
| 90 | +You can submit feedback on the current roadmap by creating a :ref:`community topic<creating_community_topic>`. |
| 91 | + |
| 92 | +Visit the :ref:`Ansible communication guide<communication>` for details on how to join and use Ansible communication platforms. |
0 commit comments