Hi all- we're happy to announce that the general release of Ansible 2.7.10 and 2.6.16 is now available!
How do you get it? ------------------ $ pip install ansible==2.7.10 --user or $ pip install ansible==2.6.16 --user The tar.gz of the release can be found here: * 2.7.10 https://releases.ansible.com/ansible/ansible-2.7.10.tar.gz SHA256: 84a42d1e371c4222c82e575cb6961fafd3afe920d84e4b6d87affabe400be294 * 2.6.16 https://releases.ansible.com/ansible/ansible-2.6.16.tar.gz SHA256: e883fe2a662bdd1f6e8bbe03caf1d8466fda6caba2a771528dc17b31a91d2716 What's new in 2.7.10 and 2.6.16 ------------------------------- These releases are maintenance release containing numerous bugfixes. The full changelogs are at: * 2.7.10 https://github.com/ansible/ansible/blob/stable-2.7/changelogs/CHANGELOG-v2.7.rst * 2.6.16 https://github.com/ansible/ansible/blob/stable-2.6/changelogs/CHANGELOG-v2.6.rst What's the schedule for future maintenance releases? ---------------------------------------------------- A few non-standard things to note about future maintenance releases this time around: * As you may be aware, 2.8.0-alpha1 is scheduled to come out very soon, with 2.8.0 final scheduled for mid-May. The run up to 2.8.0 final includes many prereleases so there will be quite a bit of work for release engineering to do. As such, the next maintenance release for 2.7.x (2.7.11) and 2.6.x (2.6.17) will come after 2.8.0 final is out. If 2.8.0 does not slip further, those releases will come out on May 23rd. * 2.7.11 and 2.6.17 will also mark the transition from regularly scheduled maintenance releases for those two branches to as-needed releases. 2.7.x will have further releases if there's a bugfix deemed critical while 2.6.x will have further releases if there's a security bug that needs fixing.[1]_ * For contributors, this means that those wanting to get bugfixes in to 2.7.x or 2.6.x should get it merged to devel and the backport merged to the stable branch before May 20th. This is the date that the backport needs to be merged so you should try to have the backport PR opened well before that. Otherwise you may not have time to address any problems that are noticed in the backport before May 20th has come and gone. .. [1]_: If you want more information about the lifecycle of an Ansible release, please see: https://docs.ansible.com/ansible/devel/reference_appendices/release_and_maintenance.html#development-and-stable-version-maintenance-workflow Porting Help ------------ We've published a porting guide at https://docs.ansible.com/ansible/devel/porting_guides/porting_guide_2.7.html to help migrate your content to 2.7. If you discover any errors or if any of your working playbooks break when you upgrade to 2.7.10, please use the following link to report the regression: https://github.com/ansible/ansible/issues/new/choose In your issue, be sure to mention the Ansible version that works and the one that doesn't. 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. For more options, visit https://groups.google.com/d/optout.
