"Fossies" - the Fresh Open Source Software Archive 
Source code changes of the file "docs/docsite/rst/roadmap/COLLECTIONS_7.rst" between
ansible-2.14.0.tar.gz and ansible-2.14.1rc1.tar.gz
About: Ansible is an IT Configuration Management, Deployment & Orchestration tool. Release candidate.
| COLLECTIONS_7.rst (ansible-2.14.0) | : | COLLECTIONS_7.rst (ansible-2.14.1rc1) | ||
|---|---|---|---|---|
| skipping to change at line 27 | skipping to change at line 27 | |||
| :2022-09-27: Ansible-7.0.0 alpha1 (roughly biweekly ``ansible`` alphas timed to coincide with ``ansible-core-2.14`` pre-releases). | :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 release s that beta1 should try to accommodate. | :2022-10-12: Community topic: List any backwards incompatible collection release s that beta1 should try to accommodate. | |||
| :2022-10-17: First ansible-core 2.14 release candidate. | :2022-10-17: First ansible-core 2.14 release candidate. | |||
| :2022-10-25: Ansible-7.0.0 alpha2. | :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-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: Ansible-core-2.14.0 released. | |||
| :2022-11-07: Last day for collections to make backwards incompatible releases th at will be accepted into Ansible-7. This includes adding new collections to Ansi ble 7.0.0; from now on new collections have to wait for 7.1.0 or later. | :2022-11-07: Last day for collections to make backwards incompatible releases th at will be accepted into Ansible-7. This includes adding new collections to Ansi ble 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: 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; c ollection owners and interested users should test for bugs). | :2022-11-08: Ansible-7.0.0 beta1 -- feature freeze [1]_ (weekly beta releases; c ollection owners and interested users should test for bugs). | |||
| :2022-11-15: Ansible-7.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed; t est and alert us to any blocker bugs). Blocker bugs will slip release. | :2022-11-15: Ansible-7.0.0 rc1 [2]_ [3]_ (weekly release candidates as needed; t est and alert us to any blocker bugs). Blocker bugs will slip release. | |||
| :2022-11-29: Ansible-7.0.0 release. | :2022-11-18: Last day to trigger an Ansible-7.0.0rc2 release because of major de | |||
| :2022-12-06: Release of ansible-core 2.14.1. | fects in Ansible-7.0.0rc1. | |||
| :2022-12-20: Release of Ansible-7.1.0 (bugfix + compatible features: every three | :2022-11-22: Ansible-7.0.0rc2 when necessary, otherwise Ansible-7.0.0 release. | |||
| weeks.) | :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, t his means we will freeze the semver collection versions to compatible release ve rsions. For example, if the version of community.crypto on this date was communi ty.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. | .. [1] No new modules or major features accepted after this date. In practice, t his means we will freeze the semver collection versions to compatible release ve rsions. For example, if the version of community.crypto on this date was communi ty.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 c hanges require creating a new rc and may slip the final release date. | .. [2] After this date only changes blocking a release are accepted. Accepted c hanges 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 approve d. Collection owners should discuss any blockers at a community IRC meeting (be fore 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>`_. | .. [3] Collections will only be updated to a new version if a blocker is approve d. Collection owners should discuss any blockers at a community IRC meeting (be fore 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:: | .. note:: | |||
| Breaking changes will be introduced in Ansible 7.0.0, although we encourage th e use of deprecation periods that will show up in at least one Ansible release b efore the breaking change happens, this is not guaranteed. | Breaking changes will be introduced in Ansible 7.0.0, although we encourage th e use of deprecation periods that will show up in at least one Ansible release b efore the breaking change happens, this is not guaranteed. | |||
| Ansible minor releases | 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 feat ures but not backwards incompatibilities. In practice, this means we will inclu de new collection versions where either the patch or the minor version number ha s 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.cryp to 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. Ansib le 7.x minor releases may contain new features but not backwards incompatibiliti es. In practice, this means we will include new collection versions where eithe r the patch or the minor version number has changed but not when the major numbe r 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 commu nity.crypto 3.0.0. | |||
| .. note:: | .. note:: | |||
| Minor releases will stop when Ansible-8 is released. See the :ref:`Release and Maintenance Page <release_and_maintenance>` for more information. | 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. | For more information, reach out on a mailing list or a chat channel - see :ref:` communication` for more details. | |||
| End of changes. 2 change blocks. | ||||
| 5 lines changed or deleted | 8 lines changed or added | |||