# Ansible 2.0 is here!

**URL:** <https://forum.ansible.com/t/ansible-2-0-is-here/20177>\
**Category:** Ansible Project\
**Created:** [January 12, 2016, 2:35pm UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177 "2016-01-12T14:35:00Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**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:** [January 12, 2016, 2:35pm UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177/1 "2016-01-12T14:35:00Z")

</div>

After a year of work, Ansible 2.0 is now available for download!

[http://www.ansible.com/blog/ansible-2.0-launch](http://www.ansible.com/blog/ansible-2.0-launch)

Thanks to everyone in the community who has helped with this, whether it’s been through code contributions or testing. We’ve had ~300 individual users contribute code to “v2”, not even counting the number of users contributing to the massive number of modules included in this release.

We are having a small issue updating our PPA with this release, which we’re working on correcting. We’ll send an update when that has been fixed.

Thanks again!

---

<div class="post-metadata">

**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:** [January 12, 2016, 11:14pm UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177/2 "2016-01-12T23:14:56Z")

</div>

Just a heads up, we’re going to be pushing 2.0.0.1 shortly to address a few packaging issues which were noticed today:

- Debian package failing to build due to a mistake in the changelog file.
- A directory required for the ansible-galaxy CLI command was not packaged, causing that utility to error on use.
- Re-added the taiga\_issue module, which was excluded by accident.

The new version should be ready shortly.

Thanks!

---

<div class="post-metadata">

**Author:** ![Alexander\_Taran](https://avatars.discourse-cdn.com/v4/letter/a/bbe5ce/32.png) [@Alexander\_Taran](https://forum.ansible.com/u/Alexander_Taran)\
**Post date:** [January 13, 2016, 6:56am UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177/3 "2016-01-13T06:56:14Z")

</div>

Hello!

Epel repository still contains old version. When to wait a new one?  
[https://dl.fedoraproject.org/pub/epel/7/x86\_64/repoview/ansible.html](https://dl.fedoraproject.org/pub/epel/7/x86_64/repoview/ansible.html)

### Packages

> [ansible-1.9.4-1.el7.noarch](https://dl.fedoraproject.org/pub/epel/7/x86_64/a/ansible-1.9.4-1.el7.noarch.rpm) [1.7 MiB] | **Changelog** by Kevin Fenzi (2015-10-09):  
>   
> `<br>- Update to 1.9.4<br>`  
>   
> |
> 
> - | - |

- Or how to upgrade to the latest release on CentOS 7?

Thank you, Alexander

---

<div class="post-metadata">

**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:** [January 13, 2016, 3:51pm UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177/4 "2016-01-13T15:51:59Z")

</div>

The EPEL packages usually take a few days to show up, per their regular process. If you (or anyone else) has Fedora accounts, you can test and +1 the packages to get them from epel-testing faster.

---

<div class="post-metadata">

**Author:** ![Toshio\_Kuratomi](https://avatars.discourse-cdn.com/v4/letter/t/41988e/32.png) [@Toshio\_Kuratomi](https://forum.ansible.com/u/Toshio_Kuratomi)\
**Post date:** [January 13, 2016, 5:24pm UTC](https://forum.ansible.com/t/ansible-2-0-is-here/20177/5 "2016-01-13T17:24:23Z")

</div>

You can find builds of 2.0.0.1 in the fedora update system: [https://bodhi.fedoraproject.org/updates/?packages=ansible](https://bodhi.fedoraproject.org/updates/?packages=ansible)

Fedora/EPEL updates to their package repositories are manual because they involve signing of the rpms so sometimes it can take a few days before builds of a package show up in their repositories.

Also note, Kevin Fenzi (the Fedora/EPEL ansible package maintainer) and I have been talking about how to manage this update and his current plan is to let the update sit in their updates-testing repository for quite a while to gather feedback about whether it works, breaks compatibility badly for their users, etc. So for at least a while users of fedora and EPEL will be able to get 1.9.4 from their updates repository and 2.0.x from updates-testing. (This could change in the future but it is the current plan).

-Toshio
