Ansible v2 upstream rewrite with many bugfixes and new features. See upstream changelog for details: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Ansible v2 with many bugfixes and new features. See upstream changelog for details: https://github.com/ansible/ansible/blob/devel/CHANGELOG.md
Please login to add feedback.
This update has been submitted for testing by toshio.
This update has obsoleted ansible-2.0.0.1-1.el6, and has inherited its bugs and notes.
This update has been pushed to testing.
Although I'm definitely excited for Ansible 2.0, this is not a backwards-compatible update and is not in line with the update policy. This will break many people's automation and will result in a very poor user experience.
The policy you linked does not apply to EPEL. This policy applies to EPEL
Oops! Thanks fale.
I agree with some of the other downvoters. Ansible 2.0 is great and I thank you for maintaining the package, but please only put 2.0 in Rawhide so that users don't have to port their playbooks except on a major OS upgrade as per the packaging guidelines.
I would definitely like to see 2.0 available in EPEL, but I think having a new package would be much more appropriate given the sweeping API changes.
I just tested my ansible 1.9 playbooks on 2.0 and 2.0 is not backwards-compatible.
Forgot to downvote on my last comment.
karma: -1
This is an EPEL update and is possible in EPEL to break things with the updates as explained here. Yes, there is a procedure to do, but this does not mean is not possible. Also here a post in the epel-devel ML has been done
This update has reached 14 days in testing and can be pushed to stable now if the maintainer wishes
This update has been obsoleted by ansible-2.0.0.2-3.el6.