diff options
Diffstat (limited to 'docs/docsite/rst/roadmap')
20 files changed, 1127 insertions, 0 deletions
diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_2_10.rst b/docs/docsite/rst/roadmap/COLLECTIONS_2_10.rst new file mode 100644 index 0000000..72fdc9c --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_2_10.rst @@ -0,0 +1,51 @@ +==================== +Ansible project 2.10 +==================== + +This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-base <https://pypi.org/project/ansible-base/>`_ package as well. All dates are subject to change. See :ref:`base_roadmap_2_10` for the most recent updates on ansible-base. + +.. contents:: + :local: + +Release Schedule +---------------- + +.. note:: Dates subject to change. +.. note:: We plan to post weekly alpha releases to the `PyPI ansible project <https://pypi.org/project/ansible/>`_ for testing. + +.. warning:: + We initially were going to have feature freeze on 2020-08-18. We tried this but decided to + change course. Instead, we'll enter feature freeze when ansible-2.10.0 beta1 is released. + +- 2020-06-23: ansible-2.10 alpha freeze. + No net new collections will be added to the ``ansible-2.10`` package after this date. +- 2020-07-10: Ansible collections freeze date for content shuffling. + Content should be in its final collection for the ansible-2.10 series of releases. No more content should move out of the ``community.general`` or ``community.network`` collections. +- 2020-08-13: ansible-base 2.10 Release date, see :ref:`base_roadmap_2_10`. +- 2020-08-14: final ansible-2.10 alpha. +- 2020-09-01: ansible-2.10.0 beta1 and feature freeze. + + - No new modules or major features will be added 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-1.1.0; ansible-2.10.0 could ship with community-crypto-1.1.1. It would not ship with community-crypto-1.2.0. + +- 2020-09-08: ansible-2.10.0 beta2. +- 2020-09-15: ansible-2.10.0 rc1 and final freeze. + + - After this date only changes blocking a release are accepted. + - Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at the community meeting (on 9-17) to decide whether to bump the version of the collection for a fix. See the `Community meeting agenda <https://github.com/ansible/community/issues/539>`_. + +** Additional release candidates to be published as needed as blockers are fixed ** + +- 2020-09-22: ansible-2.10 GA release date. + +Ansible-2.10.x patch releases will occur roughly every three weeks if changes to collections have been made or if it is deemed necessary to force an upgrade to a later ansible-base-2.10.x. Ansible-2.10.x patch 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 (example: Ansible-2.10 ships with community-crypto-1.1.0; ansible-2.10.1 may ship with community-crypto-1.2.0 but would not ship with community-crypto-2.0.0). + + +.. note:: + + Minor releases will stop when :ref:`Ansible-3 <ansible_3_roadmap>` is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +Breaking changes may be introduced in ansible-3.0 although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before being changed incompatibly. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_3_0.rst b/docs/docsite/rst/roadmap/COLLECTIONS_3_0.rst new file mode 100644 index 0000000..e40d49c --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_3_0.rst @@ -0,0 +1,58 @@ +.. _ansible_3_roadmap: + +=================== +Ansible project 3.0 +=================== + +This release schedule includes dates for the `ansible <https://pypi.org/project/ansible/>`_ package, with a few dates for the `ansible-base <https://pypi.org/project/ansible-base/>`_ package as well. All dates are subject to change. Ansible 3.x.x includes ``ansible-base`` 2.10. See :ref:`base_roadmap_2_10` for the most recent updates on ``ansible-base``. + +.. contents:: + :local: + +Release schedule +================= + +.. note:: + + Ansible is switching from its traditional versioning scheme to `semantic versioning <https://semver.org/>`_ starting with this release. So this version is 3.0.0 instead of 2.11.0. + + + +:2020-12-16: Finalize rules for net-new collections submitted for the ansible release. +:2021-01-27: Final day for new collections to be **reviewed and approved**. They MUST be + submitted prior to this to give reviewers a chance to look them over and for collection owners + to fix any problems. +:2021-02-02: Ansible-3.0.0-beta1 -- feature freeze [1]_ +:2021-02-09: Ansible-3.0.0-rc1 -- final freeze [2]_ [3]_ +:2021-02-16: Release of Ansible-3.0.0 +:2021-03-09: Release of Ansible-3.1.0 (bugfix + compatible features: every three 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.1.0; ansible-3.0.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0. + +.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date. +.. [3] Collections will only be updated to a new version 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 `Community meeting agenda <https://github.com/ansible/community/issues/539>`_. + + +.. note:: + + Breaking changes may be introduced in Ansible 3.0.0, although we encourage collection owners to use deprecation periods that will show up in at least one Ansible release before the breaking change happens. + + +Ansible minor releases +======================= + +Ansible 3.x.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-base-2.10.x. Ansible 3.x.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-3.0.0 ships with community-crypto-2.1.0; Ansible-3.1.0 may ship with community-crypto-2.2.0 but would not ship with community-crypto-3.0.0). + + +.. note:: + + Minor releases will stop when :ref:`Ansible-4 <ansible_4_roadmap>` is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. + + +ansible-base release +==================== + +Ansible 3.x.x works with ``ansible-base`` 2.10. See :ref:`base_roadmap_2_10` for details. diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_4.rst b/docs/docsite/rst/roadmap/COLLECTIONS_4.rst new file mode 100644 index 0000000..2bcebb5 --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_4.rst @@ -0,0 +1,55 @@ +.. _ansible_4_roadmap: + +=================== +Ansible project 4.0 +=================== + +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 :ref:`base_roadmap_2_11` for the most recent updates on ``ansible-core``. + +.. contents:: + :local: + + +Release schedule +================= + + +:2021-01-26: New Collections will be reviewed for inclusion in Ansible 4. Submit a request to include a new collection in this `GitHub Discussion <https://github.com/ansible-collections/ansible-inclusion/discussions/new>`_. +:2021-03-03: Ansible-4.0.0 alpha1 (biweekly ``ansible`` alphas. These are timed to coincide with the start of the ``ansible-core-2.11`` pre-releases). +:2021-03-16: Ansible-4.0.0 alpha2 +:2021-03-30: Ansible-4.0.0 alpha3 +:2021-04-13: Last day for new collections to be submitted for inclusion in Ansible 4. Note that collections MUST be reviewed and approved before being included. There is no guarantee that we will review every collection. The earlier your collection is submitted, the more likely it will be that your collection will be reviewed and the necessary feedback can be addressed in time for inclusion. +:2021-04-13: Ansible-4.0.0 alpha4 +:2021-04-14: Community Meeting topic: list any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate. +:2021-04-21: Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline. +:2021-04-26: Last day for new collections to be **reviewed and approved** for inclusion in Ansible 4. +:2021-04-26: Last day for collections to make backwards incompatible releases that will be accepted into Ansible 4. +:2021-04-27: Ansible-4.0.0 beta1 -- feature freeze [1]_ (weekly beta releases. Collection owners and interested users should test for bugs). +:2021-05-04: Ansible-4.0.0 beta2 +:2021-05-11: Ansible-4.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed. Test and alert us to any blocker bugs). +:2021-05-18: Ansible-4.0.0 release +:2021-06-08: Release of Ansible-4.1.0 (bugfix + compatible features: every three 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.1.0; ansible-3.0.0 could ship with community-crypto-2.1.1. It would not ship with community-crypto-2.2.0. + +.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date. +.. [3] Collections will only be updated to a new version 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 `Community meeting agenda <https://github.com/ansible/community/issues/539>`_. + + +.. note:: + + Breaking changes will be introduced in Ansible 4.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. + + +Ansible minor releases +======================= + +Ansible 4.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.11.x. Ansible 4.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-4.0.0 ships with community-crypto-2.1.0; Ansible-4.1.0 may ship with community-crypto-2.2.0 but would not ship with community-crypto-3.0.0). + + +.. note:: + + Minor releases will stop when Ansible-5 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_5.rst b/docs/docsite/rst/roadmap/COLLECTIONS_5.rst new file mode 100644 index 0000000..9789cd8 --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_5.rst @@ -0,0 +1,58 @@ +.. _ansible_5_roadmap: + +=================== +Ansible project 5.0 +=================== + +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 :ref:`core_roadmap_2_12` for the most recent updates on ``ansible-core``. + +.. contents:: + :local: + + +Release schedule +================= + +:2021-04-14: New Collections can be reviewed for inclusion in Ansible 5. Submit a request to include a new collection in this `GitHub Discussion <https://github.com/ansible-collections/ansible-inclusion/discussions/new>`_. +:2021-09-24: ansible-core feature freeze. +:2021-09-27: Start of ansible-core 2.12 betas (weekly, as needed). +:2021-10-05: Ansible-5.0.0 alpha1 (roughly biweekly ``ansible`` alphas timed to coincide with ``ansible-core-2.12`` pre-releases). +:2021-10-12: Last day for new collections to be submitted for inclusion in Ansible-5. Collections MUST be reviewed and approved before being included. There is no guarantee that we will review every collection. The earlier your collection is submitted, the more likely it will be that your collection will be reviewed and the necessary feedback can be addressed in time for inclusion. +:2021-10-13: Community Meeting topic: List any new collection reviews which block release. List any backwards incompatible collection releases that beta1 should try to accommodate. +:2021-10-18: First ansible-core release candidate, stable-2.12 branch created. +:2021-10-19: Ansible-5.0.0 alpha2. +:2021-10-26: Last day for new collections to be **reviewed and approved** for inclusion in Ansible-5. +:2021-10-27: Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline. +:2021-11-02: Ansible-5.0.0 alpha3. +:2021-11-08: Ansible-core-2.12 released. +:2021-11-08: Last day for collections to make backwards incompatible releases that will be accepted into Ansible-5. +:2021-11-09: Create the ansible-build-data directory and files for Ansible-6. New collection approvals will target this. +:2021-11-09: Ansible-5.0.0 beta1 -- feature freeze [1]_ (weekly beta releases; collection owners and interested users should test for bugs). +:2021-11-16: Ansible-5.0.0 beta2. +:2021-11-23: Ansible-5.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release. +:2021-11-30: Ansible-5.0.0 release. +:2021-12-21: Release of Ansible-5.1.0 (bugfix + compatible features: every three 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.1.0; Ansible-5.0.0 could ship with community.crypto 2.1.1. It would not ship with community.crypto 2.2.0. + +.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date. + +.. [3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_. + +.. note:: + + Breaking changes will be introduced in Ansible 5.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. + + +Ansible minor releases +======================= + +Ansible 5.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.12.x. Ansible 5.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-5.0.0 ships with community.crypto 2.1.0; Ansible-5.1.0 may ship with community.crypto 2.2.0 but would not ship with community.crypto 3.0.0. + + +.. note:: + + Minor releases will stop when Ansible-6 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_6.rst b/docs/docsite/rst/roadmap/COLLECTIONS_6.rst new file mode 100644 index 0000000..957c989 --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_6.rst @@ -0,0 +1,65 @@ +.. _ansible_6_roadmap: + +=================== +Ansible project 6.0 +=================== + +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.13 Roadmap <https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_13.html>`_ for the most recent updates on ``ansible-core``. + +.. contents:: + :local: + + +Release schedule +================= + + +:2022-03-28: ansible-core feature freeze, stable-2.13 branch created. +:2022-04-11: Start of ansible-core 2.13 betas (biweekly, as needed). +:2022-04-12: Ansible-6.0.0 alpha1 (roughly biweekly ``ansible`` alphas timed to coincide with ``ansible-core-2.13`` pre-releases). +:2022-04-27: Community Meeting topic: List any backwards incompatible collection releases that beta1 should try to accommodate. +:2022-05-02: First ansible-core release candidate. +:2022-05-03: Ansible-6.0.0 alpha2. +:2022-05-11: Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline. +:2022-05-16: Ansible-core-2.13 released. +:2022-05-17: Ansible-6.0.0 alpha3. +:2022-05-23: Last day for collections to make backwards incompatible releases that will be accepted into Ansible-6. This includes adding new collections to Ansible 6.0.0; from now on new collections have to wait for 6.1.0 or later. +:2022-05-24: Create the ansible-build-data directory and files for Ansible-7. +:2022-05-24: Ansible-6.0.0 beta1 -- feature freeze [1]_ (weekly beta releases; collection owners and interested users should test for bugs). +:2022-05-31: Ansible-6.0.0 beta2. +:2022-06-07: Ansible-6.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed; test and alert us to any blocker bugs). Blocker bugs will slip release. +:2022-06-21: Ansible-6.0.0 release. +:2022-07-12: Release of Ansible-6.1.0 (bugfix + compatible features: every three 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-6.0.0 could ship with community.crypto 2.3.1. It would not ship with community.crypto 2.4.0. + +.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date. + +.. [3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_. + +.. note:: + + Breaking changes will be introduced in Ansible 6.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. + + +Ansible minor releases +======================= + +Ansible 6.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.13.x. Ansible 6.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-6.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:: + + Minor releases will stop when Ansible-7 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. + +Planned work +============ + +More details can be found in `the community-topics planning issue <https://github.com/ansible-community/community-topics/issues/56>`_. + +* Remove compatibility code which prevents parallel install of Ansible 6 with Ansible 2.9 or ansible-base 2.10 +* Stop installing files (such as tests and development artifacts like editor configs) we have no use for +* Ship Python wheels (as ansible-core 2.13 will likely also do) to improve installation performance diff --git a/docs/docsite/rst/roadmap/COLLECTIONS_7.rst b/docs/docsite/rst/roadmap/COLLECTIONS_7.rst new file mode 100644 index 0000000..dcd9262 --- /dev/null +++ b/docs/docsite/rst/roadmap/COLLECTIONS_7.rst @@ -0,0 +1,57 @@ +.. _ansible_7_roadmap: + +=================== +Ansible project 7.0 +=================== + +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.14 Roadmap <https://docs.ansible.com/ansible-core/devel/roadmap/ROADMAP_2_14.html>`_ for the most recent updates on ``ansible-core``. + +.. contents:: + :local: + + +Release schedule +================= + + +:2022-09-19: ansible-core feature freeze, stable-2.14 branch created. +:2022-09-26: Start of ansible-core 2.14 betas (biweekly, as needed). +:2022-09-27: Ansible-7.0.0 alpha1 (roughly biweekly ``ansible`` alphas timed to coincide with ``ansible-core-2.14`` pre-releases). +:2022-10-12: Community topic: List any backwards incompatible collection releases that beta1 should try to accommodate. +:2022-10-17: First ansible-core 2.14 release candidate. +:2022-10-25: Ansible-7.0.0 alpha2. +:2022-10-26: Community Meeting topic: Decide what contingencies to activate for any blockers that do not meet the deadline. +:2022-11-07: Ansible-core-2.14.0 released. +:2022-11-07: Last day for collections to make backwards incompatible releases that will be accepted into Ansible-7. This includes adding new collections to Ansible 7.0.0; from now on new collections have to wait for 7.1.0 or later. +: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-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. + +.. [2] After this date only changes blocking a release are accepted. Accepted changes require creating a new rc and may slip the final release date. + +.. [3] Collections will only be updated to a new version if a blocker is approved. Collection owners should discuss any blockers at a community IRC meeting (before this freeze) to decide whether to bump the version of the collection for a fix. See the `Community IRC meeting agenda <https://github.com/ansible/community/issues/539>`_. + +.. note:: + + Breaking changes will be introduced in Ansible 7.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. + + +Ansible minor releases +======================= + +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-7.1.0 may ship with community.crypto 2.4.0 but would not ship with community.crypto 3.0.0. + + +.. note:: + + Minor releases will stop when Ansible-8 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. + + +For more information, reach out on a mailing list or a chat channel - see :ref:`communication` for more details. diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_10.rst b/docs/docsite/rst/roadmap/ROADMAP_2_10.rst new file mode 100644 index 0000000..d303ca4 --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_10.rst @@ -0,0 +1,51 @@ +.. _base_roadmap_2_10: + +================= +Ansible-base 2.10 +================= + +.. contents:: + :local: + +Release Schedule +---------------- + +Expected +======== + +PRs must be raised well in advance of the dates below to have a chance of being included in this ansible-base release. + +.. note:: There is no Alpha phase in 2.10. +.. note:: Dates subject to change. + +- 2020-06-16 Beta 1 **Feature freeze** + No new functionality (including modules/plugins) to any code + +- 2020-07-21 Release Candidate 1 (bumped from 2020-07-14) +- 2020-07-24 Release Candidate 2 +- 2020-07-25 Release Candidate 3 +- 2020-07-30 Release Candidate 4 +- 2020-08-13 Release + +Release Manager +--------------- + +@sivel + +Planned work +============ + +- Migrate non-base plugins and modules from the ``ansible/ansible`` repository to smaller collection repositories +- Add functionality to ease transition to collections, such as automatic redirects from the 2.9 names to the new FQCN of the plugin +- Create new ``ansible-base`` package representing the ``ansible/ansible`` repository + +Additional Resources +==================== + +The 2.10 release of Ansible will fundamentally change the scope of plugins included in the ``ansible/ansible`` repository, by +moving much of the plugins into smaller collection repositories that will be shipped through https://galaxy.ansible.com/ + +The following links have more information about this process: + +- https://groups.google.com/d/msg/ansible-devel/oKqgCeYTs-M/cHrOgMw8CAAJ +- https://github.com/ansible-collections/overview/blob/main/README.rst diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_11.rst b/docs/docsite/rst/roadmap/ROADMAP_2_11.rst new file mode 100644 index 0000000..3fa3b6b --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_11.rst @@ -0,0 +1,48 @@ +.. _base_roadmap_2_11: + +================= +Ansible-core 2.11 +================= + +.. contents:: + :local: + +Release Schedule +---------------- + +Expected +======== + +PRs must be raised well in advance of the dates below to have a chance of being included in this ansible-core release. + +.. note:: There is no Alpha phase in 2.11. +.. note:: Dates subject to change. + +- 2021-02-12 Feature Freeze + No new functionality (including modules/plugins) to any code + +- 2021-03-02 Beta 1 +- 2021-03-15 Beta 2 (if necessary) + +- 2021-03-29 Release Candidate 1 (and ``stable-2.11`` branching from ``devel``) +- 2021-04-12 Release Candidate 2 (if necessary) + +- 2021-04-26 Release + +Release Manager +--------------- + + Ansible Core Team + +Planned work +============ + +- Rename ``ansible-base`` to ``ansible-core``. +- Improve UX of ``ansible-galaxy collection`` CLI, specifically as it relates to install and upgrade. +- Add new Role Argument Spec feature that will allow a role to define an argument spec to be used in + validating variables used by the role. +- Bump the minimum Python version requirement for the controller to Python 3.8. There will be no breaking changes + to this release, however ``ansible-core`` will only be packaged for Python 3.8+. ``ansible-core==2.12`` will include + breaking changes requiring at least Python 3.8. +- Introduce split-controller testing in ``ansible-test`` to separate dependencies for the controller from + dependencies on the target. diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_12.rst b/docs/docsite/rst/roadmap/ROADMAP_2_12.rst new file mode 100644 index 0000000..c0a7ccd --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_12.rst @@ -0,0 +1,50 @@ +.. _core_roadmap_2_12: + +================= +Ansible-core 2.12 +================= + +.. contents:: + :local: + +Release Schedule +---------------- + +Expected +======== + +PRs must be raised well in advance of the dates below to have a chance of being included in this ansible-core release. + +.. note:: There is no Alpha phase in 2.12. +.. note:: Dates subject to change. + +- 2021-09-24 Feature Freeze (and ``stable-2.12`` branching from ``devel``) + No new functionality (including modules/plugins) to any code + +- 2021-09-27 Beta 1 +- 2021-10-04 Beta 2 (if necessary) + +- 2021-10-18 Release Candidate 1 +- 2021-10-25 Release Candidate 2 (if necessary) + +- 2021-11-08 Release + +Release Manager +--------------- + + Ansible Core Team + +Planned work +============ + +- Bump the minimum Python version requirement for the controller to Python 3.8. This will be a hard requirement. +- Deprecate Python 2.6 support for managed/target hosts. The release of ``ansible-core==2.13`` will remove Python 2.6 support. +- Introduce split-controller testing in ``ansible-test`` to separate dependencies for the controller from dependencies on the target. +- Extend the functionality of ``module_defaults`` ``action_groups`` to be created and presented by collections. + +Delayed work +============ + +The following work has been delayed and retargeted for a future release + +- Implement object proxies, to expose restricted interfaces between parts of the code, and enable deprecations of attributes and variables. diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_13.rst b/docs/docsite/rst/roadmap/ROADMAP_2_13.rst new file mode 100644 index 0000000..00b994a --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_13.rst @@ -0,0 +1,65 @@ +.. _core_roadmap_2_13: + +***************** +Ansible-core 2.13 +***************** + +.. contents:: + :local: + +Release Schedule +================ + +Expected +-------- + +PRs must be raised well in advance of the dates below to have a chance of being included in this ansible-core release. + +.. note:: There is no Alpha phase in 2.13. +.. note:: Dates subject to change. + +Development Phase +^^^^^^^^^^^^^^^^^ + +The ``milestone`` branch will be advanced at the start date of each development phase. + +- 2021-09-27 Development Phase 1 +- 2021-12-13 Development Phase 2 +- 2022-02-14 Development Phase 3 + +Release Phase +^^^^^^^^^^^^^ + +- 2022-03-28 Feature Freeze (and ``stable-2.13`` branching from ``devel``) + No new functionality (including modules/plugins) to any code + +- 2022-04-11 Beta 1 +- 2022-04-25 Beta 2 (if necessary) + +- 2022-05-02 Release Candidate 1 + +- 2022-05-16 Release + +Release Manager +=============== + + Ansible Core Team + +Planned work +============ + +* ``ansible-doc`` extended dump support for devtools integration +* ``ansible-galaxy`` CLI collection verification, source, and trust +* ``jinja2`` 3.0+ dependency +* Consolidate template handling to always use ``jinja2`` native +* Drop Python 2.6 support for module execution +* Update the collection loader to Python 3.x loader API, due to removal of the Python 2 API in Python 3.12 +* Modernize python packaging and installation + +Delayed work +============ + +The following work has been delayed and retargeted for a future release + +* Data Tagging +* Implement sidecar docs to support documenting filter/test plugins, as well as non Python modules diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_14.rst b/docs/docsite/rst/roadmap/ROADMAP_2_14.rst new file mode 100644 index 0000000..0f0bbea --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_14.rst @@ -0,0 +1,63 @@ +.. _core_roadmap_2.14: + +***************** +Ansible-core 2.14 +***************** + +.. contents:: + :local: + +Release Schedule +================ + +Expected +-------- + +PRs must be raised well in advance of the dates below to have a chance of being included in this ansible-core release. + +.. note:: Dates subject to change. + +Development Phase +^^^^^^^^^^^^^^^^^ + +The ``milestone`` branch will be advanced at the start date of each development phase. + +- 2022-05-02 Development Phase 1 +- 2022-06-27 Development Phase 2 +- 2022-08-08 Development Phase 3 + +Release Phase +^^^^^^^^^^^^^ + +- 2022-09-19 Feature Freeze (and ``stable-2.14`` branching from ``devel``) + No new functionality (including modules/plugins) to any code + +- 2022-09-26 Beta 1 + +- 2022-10-17 Release Candidate 1 + +- 2022-11-07 Release + +.. note:: The beta and release candidate schedules allow for up to 3 releases on a weekly schedule depending on the necessity of creating a release. + +Release Manager +=============== + + Ansible Core Team + +Planned work +============ + +* Implement sidecar docs to support documenting filter/test plugins, as well as non Python modules +* Proxy Display over queue from forks +* Move handler processing into new PlayIterator phase to use the configured strategy +* Convert FieldAttribute to data descriptors to avoid complex meta classes +* Drop Python 3.8 support for controller +* Enforce running controller code with the Python locale and filesystem encoding set to UTF-8 + +Delayed work +============ + +The following work has been delayed and retargeted for a future release: + +* Data Tagging diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_5.rst b/docs/docsite/rst/roadmap/ROADMAP_2_5.rst new file mode 100644 index 0000000..802a479 --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_5.rst @@ -0,0 +1,142 @@ +=========== +Ansible 2.5 +=========== +**Core Engine Freeze and Module Freeze: 22 January 2018** + +**Core and Curated Module Freeze: 22 January 2018** + +**Community Module Freeze: 7 February 2018** + +**Release Candidate 1 will be 21 February, 2018** + +**Target: March 2018** + +**Service Release schedule: every 2-3 weeks** + +.. contents:: Topics + +Release Manager +--------------- +Matt Davis (IRC/GitHub: @nitzmahone) + + +Engine improvements +------------------- +- Assemble module improvements + - assemble just skips when in check mode, it should be able to test if there is a difference and changed=true/false. + - The same with diff, it should work as template modules does +- Handle Password reset prompts cleaner +- Tasks stats for rescues and ignores +- Normalize temp dir usage across all subsystems +- Add option to set playbook dir for adhoc, inventory and console to allow for 'relative path loading' + + +Ansible-Config +-------------- +- Extend config to more plugin types and update plugins to support the new config + +Inventory +--------- +- ansible-inventory option to output group variable assignment and data (--export) +- Create inventory plugins for: + - aws + +Facts +----- +- Namespacing fact variables (via a config option) implemented in ansible/ansible PR `#18445 <https://github.com/ansible/ansible/pull/18445>`_. + Proposal found in ansible/proposals issue `#17 <https://github.com/ansible/proposals/issues/17>`_. +- Make fact collectors and gather_subset specs finer grained +- Eliminate unneeded deps between fact collectors +- Allow fact collectors to indicate if they need information from another fact collector to be gathered first. + +Static Loop Keyword +------------------- + +- A simpler alternative to ``with_``, ``loop:`` only takes a list +- Remove complexity from loops, lookups are still available to users +- Less confusing having a static directive vs a one that is dynamic depending on plugins loaded. + +Vault +----- +- Vault secrets client inc new 'keyring' client + +Runtime Check on Modules for Disabling +-------------------------------------- +- Filter on things like "supported_by" in module metadata +- Provide users with an option of "warning, error or allow/ignore" +- Configurable via ansible.cfg and environment variable + +Windows +------- +- Implement gather_subset on Windows facts +- Fix Windows async + become to allow them to work together +- Implement Windows become flags for controlling various modes **(done)** + - logontype + - elevation behavior +- Convert win_updates to action plugin for auto reboot and extra features **(done)** +- Spike out changing the connection over to PSRP instead of WSMV **(done- it's possible)** +- Module updates + + - win_updates **(done)** + + - Fix win_updates to detect (or request) become + - Add enable/disable features to win_updates + - win_dsc further improvements **(done)** + +General Cloud +------------- +- Make multi-cloud provisioning easier +- Diff mode will output provisioning task results of ansible-playbook runs +- Terraform module + +AWS +--- +- Focus on pull requests for various modules +- Triage existing merges for modules +- Module work + + - ec2_instance + - ec2_vpc: Allow the addition of secondary IPv4 CIDRS to existing VPCs. + - AWS Network Load Balancer support (NLB module, ASG support, and so on) + - rds_instance + +Azure +----- +- Azure CLI auth **(done)** +- Fix Azure module results to have "high-level" output instead of raw REST API dictionary **(partial, more to come in 2.6)** +- Deprecate Azure automatic storage accounts in azure_rm_virtualmachine **(breaks on Azure Stack, punted until AS supports managed disks)** + +Network Roadmap +--------------- +- Refactor common network shared code into package **(done)** +- Convert various nxos modules to use declarative intent **(done)** +- Refactor various modules to use the cliconf plugin **(done)** +- Add various missing declarative modules for supported platforms and functions **(done)** +- Implement a feature that handles platform differences and feature unavailability **(done)** +- netconf-config.py should provide control for deployment strategy +- Create netconf connection plugin **(done)** +- Create netconf fact module +- Turn network_cli into a usable connection type **(done)** +- Implements jsonrpc message passing for ansible-connection **(done)** +- Improve logging for ansible-connection **(done)** +- Improve stdout output for failures whilst using persistent connection **(done)** +- Create IOS-XR NetConf Plugin and refactor iosxr modules to use netconf plugin **(done)** +- Refactor junos modules to use netconf plugin **(done)** +- Filters: Add a filter to convert XML response from a network device to JSON object **(done)** + +Documentation +------------- +- Extend documentation to more plugins +- Document vault-password-client scripts. +- Network Documentation + + - New landing page (to replace intro_networking) **(done)** + - Platform specific guides **(done)** + - Walk through: Getting Started **(done)** + - Networking and ``become`` **(done)** + - Best practice **(done)** + +Contributor Quality of Life +--------------------------- +- Finish PSScriptAnalyer integration with ansible-test (for enforcing Powershell style) **(done)** +- Resolve issues requiring skipping of some integration tests on Python 3. diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_6.rst b/docs/docsite/rst/roadmap/ROADMAP_2_6.rst new file mode 100644 index 0000000..7d8226e --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_6.rst @@ -0,0 +1,82 @@ +=========== +Ansible 2.6 +=========== + +.. contents:: Topics + +Release Schedule +---------------- + +Actual +====== + +- 2018-05-17 Core Freeze (Engine and Core Modules/Plugins) +- 2018-05-21 Alpha Release 1 +- 2018-05-25 Community Freeze (Non-Core Modules/Plugins) +- 2018-05-25 Branch stable-2.6 +- 2018-05-30 Alpha Release 2 +- 2018-06-05 Release Candidate 1 +- 2018-06-08 Release Candidate 2 +- 2018-06-18 Release Candidate 3 +- 2018-06-25 Release Candidate 4 +- 2018-06-26 Release Candidate 5 +- 2018-06-28 Final Release + + +Release Manager +--------------- +* 2.6.0-2.6.12 Matt Clay (IRC/GitHub: @mattclay) +* 2.6.13+ Toshio Kuratomi (IRC: abadger1999; GitHub: @abadger) + + +Engine improvements +------------------- + +- Version 2.6 is largely going to be a stabilization release for Core code. +- Some of the items covered in this release, but are not limited to are the following: + + - ``ansible-inventory`` + - ``import_*`` + - ``include_*`` + - Test coverage + - Performance Testing + +Core Modules +------------ +- Adopt-a-module Campaign + + - Review current status of all Core Modules + - Reduce backlog of open issues against these modules + +Cloud Modules +------------- + +Network +------- + +Connection work +================ + +* New connection plugin: eAPI `proposal#102 <https://github.com/ansible/proposals/issues/102>`_ +* New connection plugin: NX-API +* Support for configurable options for network_cli & netconf + +Modules +======= + +* New ``net_get`` - platform independent module for pulling configuration via SCP/SFTP over network_cli +* New ``net_put`` - platform independent module for pushing configuration via SCP/SFTP over network_cli +* New ``netconf_get`` - Netconf module to fetch configuration and state data `proposal#104 <https://github.com/ansible/proposals/issues/104>`_ + +Other Features +================ + +* Stretch & tech preview: Configuration caching for network_cli. Opt-in feature to avoid ``show running`` performance hit + + +Windows +------- + + + + diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_7.rst b/docs/docsite/rst/roadmap/ROADMAP_2_7.rst new file mode 100644 index 0000000..bf65dcf --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_7.rst @@ -0,0 +1,109 @@ +=========== +Ansible 2.7 +=========== + +.. contents:: Topics + +Release Schedule +---------------- + +Expected +======== + +- 2018-08-23 Core Freeze (Engine and Core Modules/Plugins) +- 2018-08-23 Alpha Release 1 +- 2018-08-30 Community Freeze (Non-Core Modules/Plugins) +- 2018-08-30 Beta Release 1 +- 2018-09-06 Release Candidate 1 (If needed) +- 2018-09-13 Release Candidate 2 (If needed) +- 2018-09-20 Release Candidate 3 (If needed) +- 2018-09-27 Release Candidate 4 (If needed) +- 2018-10-04 General Availability + +Release Manager +--------------- +Toshio Kuratomi (IRC: abadger1999; GitHub: @abadger) + + +Cleaning Duty +------------- + +- Drop Py2.6 for controllers `Docs PR #42971 <https://github.com/ansible/ansible/pull/42971>`_ and + `issue #42972 <https://github.com/ansible/ansible/issues/42972>`_ +- Remove dependency on simplejson `issue #42761 <https://github.com/ansible/ansible/issues/42761>`_ + + +Engine Improvements +------------------- + +- Performance improvement invoking Python modules `pr #41749 <https://github.com/ansible/ansible/pull/41749>`_ +- Jinja native types will allow for users to render a Python native type. `pr #32738 <https://github.com/ansible/ansible/pull/32738>`_ + + +Core Modules +------------ + +- Include feature changes and improvements + + - Create new argument ``apply`` that will allow for included tasks to inherit explicitly provided attributes. `pr #39236 <https://github.com/ansible/ansible/pull/39236>`_ + - Create "private" functionality for allowing vars/default to be exposed outside of roles. `pr #41330 <https://github.com/ansible/ansible/pull/41330>`_ +- Provide a parameter for the ``template`` module to output to different encoding formats `pr + #42171 <https://github.com/ansible/ansible/pull/42171>`_ +- ``reboot`` module for Linux hosts (@samdoran) `pr #35205 <https://github.com/ansible/ansible/pull/35205>`_ + +Cloud Modules +------------- + +General +======= +* Cloud auth plugin `proposal #24 <https://github.com/ansible/proposals/issues/24>`_ + +AWS +=== +* Inventory plugin for RDS `pr #41919 <https://github.com/ansible/ansible/pull/41919>`_ +* Count support for `ec2_instance` +* `aws_eks` module `pr #41183 <https://github.com/ansible/ansible/pull/41183>`_ +* Cloudformation stack sets support (`PR#41669 <https://github.com/ansible/ansible/pull/41669>`_) +* RDS instance and snapshot modules `pr #39994 <https://github.com/ansible/ansible/pull/39994>`_ `pr #43789 <https://github.com/ansible/ansible/pull/43789>`_ +* Diff mode improvements for cloud modules `pr #44533 <https://github.com/ansible/ansible/pull/44533>`_ + +Azure +===== + +* Azure inventory plugin `issue #42769 <https://github.com/ansible/ansible/issues/42769>`__ + + +Network +------- + +General +======= + +* Refactor the APIs in cliconf (`issue #39056 <https://github.com/ansible/ansible/issues/39056>`_) and netconf (`issue #39160 <https://github.com/ansible/ansible/issues/39160>`_) plugins so that they have a uniform signature across supported network platforms. **done** + (`PR #41846 <https://github.com/ansible/ansible/pull/41846>`_) (`PR #43643 <https://github.com/ansible/ansible/pull/43643>`_) (`PR #43837 <https://github.com/ansible/ansible/pull/43837>`_) + (`PR #43203 <https://github.com/ansible/ansible/pull/43203>`_) (`PR #42300 <https://github.com/ansible/ansible/pull/42300>`_) (`PR #44157 <https://github.com/ansible/ansible/pull/44157>`_) + +Modules +======= + +* New ``cli_config`` module `issue #39228 <https://github.com/ansible/ansible/issues/39228>`_ **done** `PR #42413 <https://github.com/ansible/ansible/pull/42413>`_. +* New ``cli_command`` module `issue #39284 <https://github.com/ansible/ansible/issues/39284>`_ +* Refactor ``netconf_config`` module to add additional functionality. **done** `proposal #104 <https://github.com/ansible/proposals/issues/104>`_ (`PR #44379 <https://github.com/ansible/ansible/pull/44379>`_) + +Windows +------- + +General +======= + +* Added new connection plugin that uses PSRP as the connection protocol `pr #41729 <https://github.com/ansible/ansible/pull/41729>`__ + +Modules +======= + +* Revamp Chocolatey to fix bugs and support offline installation `pr #43013 <https://github.com/ansible/ansible/pull/43013>`_. +* Add Chocolatey modules that can manage the following Chocolatey features + + * `Sources <https://chocolatey.org/docs/commands-sources>`_ `pr #42790 <https://github.com/ansible/ansible/pull/42790>`_ + * `Features <https://chocolatey.org/docs/chocolatey-configuration#features>`_ `pr #42848 <https://github.com/ansible/ansible/pull/42848>`_ + * `Config <https://chocolatey.org/docs/chocolatey-configuration#config-settings>`_ `pr #42915 <h*ttps://github.com/ansible/ansible/pull/42915>`_ diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_8.rst b/docs/docsite/rst/roadmap/ROADMAP_2_8.rst new file mode 100644 index 0000000..04977aa --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_8.rst @@ -0,0 +1,38 @@ +=========== +Ansible 2.8 +=========== + +.. contents:: + :local: + +Release Schedule +---------------- + +Expected +======== + +PRs must be raised well in advance of the dates below to have a chance of being included in this Ansible release. + +- 2019-04-04 Alpha 1 **Core freeze** + No new features to ``support:core`` code. + Includes no new options to existing Core modules + +- 2019-04-11 Beta 1 **Feature freeze** + No new functionality (including modules/plugins) to any code + +- 2019-04-25 Release Candidate 1 +- 2019-05-02 Release Candidate 2 +- 2019-05-10 Release Candidate 3 +- 2019-05-16 Release + + + +Release Manager +--------------- + +Toshio Kuratomi (IRC: abadger1999; GitHub: @abadger) + +Planned work +============ + +See the `Ansible 2.8 Project Board <https://github.com/ansible/ansible/projects/30>`_ diff --git a/docs/docsite/rst/roadmap/ROADMAP_2_9.rst b/docs/docsite/rst/roadmap/ROADMAP_2_9.rst new file mode 100644 index 0000000..370930a --- /dev/null +++ b/docs/docsite/rst/roadmap/ROADMAP_2_9.rst @@ -0,0 +1,39 @@ +=========== +Ansible 2.9 +=========== + +.. contents:: + :local: + +Release Schedule +---------------- + +Expected +======== + +PRs must be raised well in advance of the dates below to have a chance of being included in this Ansible release. + +.. note:: There is no Alpha phase in 2.9. + +- 2019-08-29 Beta 1 **Feature freeze** + No new functionality (including modules/plugins) to any code + +- 2019-09-19 Release Candidate 1 +- 2019-10-03 Release Candidate 2 +- 2019-10-10 Release Candidate 3 +- 2019-10-17 Release Candidate 4 (if needed) +- 2019-10-24 Release Candidate 5 (if needed) +- 2019-10-31 Release + + + +Release Manager +--------------- +TBD + +Temporarily, Matt Davis (@nitzmahone) or Matt Clay (@mattclay) on IRC or github. + +Planned work +============ + +See the `Ansible 2.9 Project Board <https://github.com/ansible/ansible/projects/34>`_ diff --git a/docs/docsite/rst/roadmap/ansible_core_roadmap_index.rst b/docs/docsite/rst/roadmap/ansible_core_roadmap_index.rst new file mode 100644 index 0000000..18f8c3a --- /dev/null +++ b/docs/docsite/rst/roadmap/ansible_core_roadmap_index.rst @@ -0,0 +1,32 @@ +.. _roadmaps: +.. _ansible_core_roadmaps: + +ansible-core Roadmaps +===================== + +The ``ansible-core`` team develops a roadmap for each major and minor ``ansible-core`` release. The latest roadmap shows current work; older roadmaps provide a history of the project. We don't publish roadmaps for subminor versions. So 2.10 and 2.11 have roadmaps, but 2.10.1 does not. + +We incorporate team and community feedback in each roadmap, and aim for further transparency and better inclusion of both community desires and submissions. + +Each roadmap offers a *best guess*, based on the ``ansible-core`` team's experience and on requests and feedback from the community, of what will be included in a given release. However, some items on the roadmap may be dropped due to time constraints, lack of community maintainers, and so on. + +Each roadmap is published both as an idea of what is upcoming in ``ansible-core``, and as a medium for seeking further feedback from the community. + +You can submit feedback on the current roadmap in multiple ways: + +- Edit the agenda of an `Core Team Meeting <https://github.com/ansible/community/blob/main/meetings/README.md>`_ (preferred) +- Post on the ``#ansible-devel`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) +- Email the ansible-devel list + +See :ref:`Ansible communication channels <communication>` for details on how to join and use the email lists and chat channels. + +.. toctree:: + :maxdepth: 1 + :glob: + :caption: ansible-core Roadmaps + + ROADMAP_2_14 + ROADMAP_2_13 + ROADMAP_2_12 + ROADMAP_2_11 + ROADMAP_2_10 diff --git a/docs/docsite/rst/roadmap/ansible_roadmap_index.rst b/docs/docsite/rst/roadmap/ansible_roadmap_index.rst new file mode 100644 index 0000000..0bdd69d --- /dev/null +++ b/docs/docsite/rst/roadmap/ansible_roadmap_index.rst @@ -0,0 +1,33 @@ +.. _roadmaps: +.. _ansible_roadmaps: + +Ansible Roadmap +=============== + +The Ansible team develops a roadmap for each major and minor Ansible release. The latest roadmap shows current work; older roadmaps provide a history of the project. We don't publish roadmaps for subminor versions. So 2.10 and 2.11 have roadmaps, but 2.10.1 does not. + +We incorporate team and community feedback in each roadmap, and aim for further transparency and better inclusion of both community desires and submissions. + +Each roadmap offers a *best guess*, based on the Ansible team's experience and on requests and feedback from the community, of what will be included in a given release. However, some items on the roadmap may be dropped due to time constraints, lack of community maintainers, and so on. + +Each roadmap is published both as an idea of what is upcoming in Ansible, and as a medium for seeking further feedback from the community. + +You can submit feedback on the current roadmap in multiple ways: + +- Edit the agenda of an `Ansible Community Meeting <https://github.com/ansible/community/issues/539>`_ (preferred) +- Post on the ``#ansible-community`` chat channel (using Matrix at ansible.im or using IRC at `irc.libera.chat <https://libera.chat/>`_) + +See :ref:`Ansible communication channels <communication>` for details on how to join and use our chat channels. + +.. toctree:: + :maxdepth: 1 + :glob: + :caption: Ansible Release Roadmaps + + COLLECTIONS_7 + COLLECTIONS_6 + COLLECTIONS_5 + COLLECTIONS_4 + COLLECTIONS_3_0 + COLLECTIONS_2_10 + old_roadmap_index diff --git a/docs/docsite/rst/roadmap/index.rst b/docs/docsite/rst/roadmap/index.rst new file mode 100644 index 0000000..0b5b4bd --- /dev/null +++ b/docs/docsite/rst/roadmap/index.rst @@ -0,0 +1,12 @@ +.. _roadmaps: + +Roadmaps +=============== + +.. toctree:: + :maxdepth: 1 + :glob: + + ansible_roadmap_index + ansible_core_roadmap_index + old_roadmap_index diff --git a/docs/docsite/rst/roadmap/old_roadmap_index.rst b/docs/docsite/rst/roadmap/old_roadmap_index.rst new file mode 100644 index 0000000..78769f1 --- /dev/null +++ b/docs/docsite/rst/roadmap/old_roadmap_index.rst @@ -0,0 +1,19 @@ +.. _old_roadmaps: + +Older Roadmaps +=============== + +Older roadmaps are listed here to provide a history of the Ansible project. + +See :ref:`roadmaps` to find current Ansible and ``ansible-base`` roadmaps. + +.. toctree:: + :maxdepth: 1 + :glob: + :caption: Older Roadmaps + + ROADMAP_2_9 + ROADMAP_2_8 + ROADMAP_2_7 + ROADMAP_2_6 + ROADMAP_2_5 |