Hi all- **Important:** If you are upgrading from an older Ansible release, please see the `How to get it` section for an important limitation.
We're happy to announce that the ansible-2.10 package is now available! The Ansible package combines the work that went into decoupling the ansible-base package, released last month, from the Ansible plugins and the work of many contributors from the community, at numerous partner businesses, and from Ansible itself to make the decoupled content available to run on that base. Its goal is to provide users an incrementally improved featureset over Ansible-2.9 but created from multiple separate projects. For an overview of "Ansible Collections" and the differences between `ansible-base` and `ansible` please see https://github.com/ansible-collections/overview/blob/main/README.rst How to get it ------------- Due to a limitation in pip, you need to uninstall Ansible 2.9 (or earlier) before installing the 2.10 version: $ pip uninstall ansible $ pip install ansible==2.10.0 --user The tar.gz of the release can be found here: * Ansible 2.10.0 https://pypi.python.org/packages/source/a/ansible/ansible-2.10.0.tar.gz SHA256: 3aadd662ac3f04e46054c99cfe533a92ba33d97982f19e49f01dbe137f31d346 What's new in Ansible 2.10.0 ------------------------------ * Collections which have opted into being a part of the Ansible-2.10.0 unified changelog will have an entry on this page: https://github.com/ansible-community/ansible-build-data/blob/main/2.10/CHANGELOG-v2.10.rst * For other collections, consult the list of included collections in the link below and check their entry on https://galaxy.ansible.com for information about their changes. * List of collections included in the 2.10.0 release: https://github.com/ansible-community/ansible-build-data/blob/2.10.0/2.10/ansible-2.10.0.deps * You can find more information for those on https://galaxy.ansible.com/. For instance, the community.crypto collection listed in the ansible-2.10.0.deps file has a galaxy page at https://galaxy.ansible.com/community/crypto/ * Changelog for ansible-base-2.10.1 which this release of ansible installs: https://github.com/ansible/ansible/blob/stable-2.10/changelogs/CHANGELOG-v2.10.rst Caveats and known bugs -------------------------- * Due to a limitation in pip, you cannot `pip install --upgrade` from ansible-2.9 or earlier to ansible-2.10 or higher. Instead, you must explicitly use `pip uninstall ansible` before pip installing the new version. If you attempt to upgrade Ansible with pip without first uninstalling, the installer warns you to uninstall first. * The individual collections that make up the ansible-2.10.0 package can be viewed independently. However, they are not currently listed by ansible-galaxy. To view these collections with ansible-galaxy, explicitly specify where ansible has installed the collections:: COLLECTION_INSTALL=$(python -c 'import ansible, os.path ; print("%s/../ansible_collections" % os.path.dirname(ansible.__file__))') ansible-galaxy collection list -p "$COLLECTION_INSTALL" * A fix has been proposed but was not be merged for 2.10.0. This is being tracked in this bug report: https://github.com/ansible/ansible/issues/70147 *These fortios modules are not automatically redirected from their 2.9.x names to the new 2.10.x names within collections. You must modify your playbooks to use fully qualified collection names for them. You can use the documentation (https://docs.ansible.com/ansible/2.10/collections/fortinet/fortios/) for the ``fortinet.fortios`` collection to determine what the fully qualified collection names are. * fortios_address * fortios_config * fortios_firewall_DoS_policy * fortios_firewall_DoS_policy6 * fortios_ipv4_policy * fortios_switch_controller_802_1X_settings * fortios_switch_controller_security_policy_802_1X * fortios_system_firmware_upgrade * fortios_system_nd_proxy * fortios_webfilter What's the schedule for new Ansible releases after 2.10.0? ----------------------------------------------------------- * Patch releases for Ansible 2.10 * We will be releasing new ansible-2.10.x patch releases approximately every 3 weeks. * These releases will contain collections with new features as long as those features do not introduce backwards incompatibilities. * These releases will all be based on ansible-base-2.10. * Expect ansible-2.10.1 around October 13th. * We're just starting to discuss the release schedule for ansible-2.11.0. * We're tentatively thinking of releasing ansible-2.11.0, with potential backwards incompatible changes to the collections but based on ansible-base-2.10 * Currently we're thinking that this release would happen sometime early next year. * Take this information as being subject to change as we're in the early stages of discussion. Porting Help ------------- There's a unified porting guide for collections which have opted-in. You can find that at: https://github.com/ansible/ansible/blob/devel/docs/docsite/rst/porting_guides/porting_guide_2.10.rst Thanks! -Toshio Kuratomi -- You received this message because you are subscribed to the Google Groups "Ansible Development" group. To unsubscribe from this group and stop receiving emails from it, send an email to ansible-devel+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-devel/CAPrnkaT4mSBx%2Btd5hYReHtcrMmzVUVpGFyXUcLYoN3-kVpwz2w%40mail.gmail.com.
