# Ansible 2.2.0 Final has been released! **URL:** \ **Category:** Ansible Project\ **Tags:** windows\ **Created:** [November 1, 2016, 1:55pm UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933 "2016-11-01T13:55:12Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [November 1, 2016, 1:55pm UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/1 "2016-11-01T13:55:12Z")
Hi all, we’re very happy to announce that Ansible 2.2.0 has been released! This release includes many new features and improvements (from the RC1 release announcement): - Almost 200 new modules! - Major performance improvements. In many cases, you should see a 2-3x improvement over 2.1/2.0. - `include_role` now allows for roles to be executed inline with your other tasks, instead of listing them only in the `roles:` section of your plays ([http://docs.ansible.com/ansible/include\_role\_module.html](http://docs.ansible.com/ansible/include_role_module.html)) - The `listen` feature for handlers allows for much easier notifications of multiple handlers via a pub/sub mechanism ([http://docs.ansible.com/ansible/playbooks\_intro.html#handlers-running-operations-on-change](http://docs.ansible.com/ansible/playbooks_intro.html#handlers-running-operations-on-change)). - Serial batches can now be specified as a list rather than a single integer value, meaning you can do something like this to scale up serial batches: `serial: [1, 5, 10]` # the first batch will be 1 host, 2nd=5 hosts, all other batches will be 10 hosts) - Windows tasks can now use “async”, and can also now use the “environment” option to set environment variables. - Support for binary modules. - New become method: `ksu` (Kerberos su). - New meta option: `end_play`, which allows for early termination of a play without failing. - Meta tasks now support conditional statements. Here is the official announcement on our website: [https://www.ansible.com/press/ansible-22-delivers-new-automation-capabilities-for-containers-networks-and-cloud](https://www.ansible.com/press/ansible-22-delivers-new-automation-capabilities-for-containers-networks-and-cloud) As always, this update is available via PyPi and [releases.ansible.com](http://releases.ansible.com) now, and packages for distros will be available as soon as possible. Thanks and enjoy! ---
**Author:** ![igorc](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/igorc/32/5491_2.png) [@igorc](https://forum.ansible.com/u/igorc)\ **Post date:** [November 2, 2016, 12:08am UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/2 "2016-11-02T00:08:48Z")
Hi James, Although the performance improvements are welcomed, I wonder how does this stack compared to 1.9.x version? There have been discussions here, more specific [https://groups.google.com/forum/#!starred/ansible-devel/UU0Tpw-qlhY](https://groups.google.com/forum/#!starred/ansible-devel/UU0Tpw-qlhY), and couple of issues raised and outlined in your post here [https://groups.google.com/forum/#!starred/ansible-devel/TLEc1NoQ7lA](https://groups.google.com/forum/#!starred/ansible-devel/TLEc1NoQ7lA), that revel a serious problem in the very core of 2.x release. Has this been addressed in 2.2.0 and if yes how close is the 2.2 performance to the old 1.9.x branch? Thanks, Igor ---
**Author:** ![James\_Cammarata](https://avatars.discourse-cdn.com/v4/letter/j/7c8e57/32.png) [@James\_Cammarata](https://forum.ansible.com/u/James_Cammarata)\ **Post date:** [November 2, 2016, 12:22am UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/3 "2016-11-02T00:22:07Z")
Hi Igor, While 2.2 is quite a bit faster than 2.0/2.1, it does still lag a bit behind 1.9. Mainly this slowness is due to the way we’ve changed how workers are created, which in 2.0+ allows us to have strategies but does come with a hit to performance. We’ll still look at ways of improving things in the future, so any analysis/debugging of performance problems is always appreciated. Thanks! ---
**Author:** ![Mehdi\_B](https://avatars.discourse-cdn.com/v4/letter/m/e480ec/32.png) [@Mehdi\_B](https://forum.ansible.com/u/Mehdi_B)\ **Post date:** [November 2, 2016, 11:17am UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/4 "2016-11-02T11:17:44Z")
Awesome to see role\_include. I had to do that in a dirty mode including the main task and the vars from the role I wanted to include in another role. Great to see ansible 2.2.0 released. M B ---
**Author:** ![Jacob\_Weber1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Jacob\_Weber1](https://forum.ansible.com/u/Jacob_Weber1)\ **Post date:** [November 3, 2016, 8:32pm UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/5 "2016-11-03T20:32:54Z")
Just curious – how long does it usually take for new RPMs to appear on epel or epel-testing? ---
**Author:** ![nirik](https://sea1.discourse-cdn.com/ansible/user_avatar/forum.ansible.com/nirik/32/686_2.png) [@nirik](https://forum.ansible.com/u/nirik)\ **Post date:** [November 3, 2016, 9:30pm UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/6 "2016-11-03T21:30:09Z")
[https://groups.google.com/forum/#!msg/ansible-project/dm59ern73-w/SaBIVJAeBjAJ](https://groups.google.com/forum/#!msg/ansible-project/dm59ern73-w/SaBIVJAeBjAJ) kevin ---
**Author:** ![Jacob\_Weber1](https://avatars.discourse-cdn.com/v4/letter/j/94ad74/32.png) [@Jacob\_Weber1](https://forum.ansible.com/u/Jacob_Weber1)\ **Post date:** [November 3, 2016, 9:42pm UTC](https://forum.ansible.com/t/ansible-2-2-0-final-has-been-released/22933/7 "2016-11-03T21:42:25Z")
Thanks Kevin. I’ll keep an eye on the status at [https://bodhi.fedoraproject.org/updates/?like=ansible](https://bodhi.fedoraproject.org/updates/?like=ansible)