# ETA on Ansible 2.0 ? **URL:** \ **Category:** Ansible Project\ **Created:** [June 11, 2015, 2:39am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465 "2015-06-11T02:39:40Z")\ **Posts on this page:** 19\ **Page:** 1
**Author:** ![Jason\_Levitt](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jason\_Levitt](https://forum.ansible.com/u/Jason_Levitt)\ **Post date:** [June 11, 2015, 2:39am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/1 "2015-06-11T02:39:40Z")
Is there an estimated release date for Ansible 2.0 ? Cheers, J ---
**Author:** ![Greg\_DeKoenigsberg1](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Greg\_DeKoenigsberg1](https://forum.ansible.com/u/Greg_DeKoenigsberg1)\ **Post date:** [June 11, 2015, 2:29pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/2 "2015-06-11T14:29:49Z")
The answer is "when it's done", basically. It's a major refactoring effort, and we want to make sure the take the time to find, and fix, the big issues. My personal guess is July, but that's just a guess. --g ---
**Author:** ![Dan\_Swartz](https://avatars.discourse-cdn.com/v4/letter/d/439d5e/32.png) [@Dan\_Swartz](https://forum.ansible.com/u/Dan_Swartz)\ **Post date:** [July 27, 2015, 2:08pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/3 "2015-07-27T14:08:14Z")
Can we get an updated estimate? Even if it’s just a matter of days vs. weeks. Thanks. ---
**Author:** ![Greg\_DeKoenigsberg1](https://avatars.discourse-cdn.com/v4/letter/g/838e76/32.png) [@Greg\_DeKoenigsberg1](https://forum.ansible.com/u/Greg_DeKoenigsberg1)\ **Post date:** [July 27, 2015, 4:06pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/4 "2015-07-27T16:06:09Z")
> Can we get an updated estimate? Even if it's just a matter of days vs. > weeks. Thanks. Latest plan: look for a beta in early August. --g ---
**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:** [July 27, 2015, 4:06pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/5 "2015-07-27T16:06:58Z")
Hi Dan, the current plan is to have a beta release for 2.0 in early August, with an official beta tar.gz for testing available for download. If that slips, we’ll let people know. Thanks! ---
**Author:** ![Bob\_Tanner](https://avatars.discourse-cdn.com/v4/letter/b/49beb7/32.png) [@Bob\_Tanner](https://forum.ansible.com/u/Bob_Tanner)\ **Post date:** [July 29, 2015, 3:35am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/6 "2015-07-29T03:35:12Z")
Not an answer, just a comment. I’ve been running v2 inside of my git clone for awhile. Been a few issues, but they have been fixed very quickly. ---
**Author:** ![Roman\_Belyakovsky](https://avatars.discourse-cdn.com/v4/letter/r/ecae2f/32.png) [@Roman\_Belyakovsky](https://forum.ansible.com/u/Roman_Belyakovsky)\ **Post date:** [September 8, 2015, 12:25pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/7 "2015-09-08T12:25:48Z")
Any update on ETA? ---
**Author:** ![Martin2](https://avatars.discourse-cdn.com/v4/letter/m/9de053/32.png) [@Martin2](https://forum.ansible.com/u/Martin2)\ **Post date:** [September 8, 2015, 1:25pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/8 "2015-09-08T13:25:08Z")
Oh come on… you’re one year ahead. Still plenty of time until early August 🙂 (Sorry. Just. Could. Not. Resist.) ---
**Author:** ![Brian\_Coca](https://avatars.discourse-cdn.com/v4/letter/b/6de8d8/32.png) [@Brian\_Coca](https://forum.ansible.com/u/Brian_Coca)\ **Post date:** [September 8, 2015, 1:28pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/9 "2015-09-08T13:28:18Z")
We already started with the alpha releases, we hope to be on the beta soon. Since this release rewrote most of the core, we will take a bit longer to ensure everything works. ---
**Author:** ![James\_Smith](https://avatars.discourse-cdn.com/v4/letter/j/ba9def/32.png) [@James\_Smith](https://forum.ansible.com/u/James_Smith)\ **Post date:** [November 13, 2015, 2:44pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/10 "2015-11-13T14:44:55Z")
Any update on this? I see that Beta 2 is out… We’re running 1.9.4 but the digitalocean v2 API isn’t supported any more, so wondering how long we’d have to wait for stable ansible 2… ---
**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:** [November 13, 2015, 6:45pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/11 "2015-11-13T18:45:38Z")
We should have beta3 sometime soon. We're working through some performance issues that we think are too big to ship 2.0 with (some performance fixes won't go in until 2.1 but there's a few that we want to be sure we take care of in time for 2.0). Once those are out of the way we should be starting our release candidate process. -Toshio ---
**Author:** ![Jason\_Levitt](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jason\_Levitt](https://forum.ansible.com/u/Jason_Levitt)\ **Post date:** [December 9, 2015, 10:21pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/12 "2015-12-09T22:21:02Z")
RC2 is out. How many release candidates are expected? J ---
**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:** [December 10, 2015, 4:18am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/13 "2015-12-10T04:18:03Z")
At least one more. We’ve seen a slow trickle of issues reported that we’d be uncomfortable releasing 2.0 with and wouldn’t want to simply add fixes for them to the existing code and release final without getting them out to users for testing for at least a few days. -Toshio ---
**Author:** ![Jason\_Levitt](https://avatars.discourse-cdn.com/v4/letter/j/779978/32.png) [@Jason\_Levitt](https://forum.ansible.com/u/Jason_Levitt)\ **Post date:** [January 5, 2016, 5:33pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/14 "2016-01-05T17:33:59Z")
Any new news on this? J ---
**Author:** ![Jeff\_Reter](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@Jeff\_Reter](https://forum.ansible.com/u/Jeff_Reter)\ **Post date:** [January 7, 2016, 9:00am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/15 "2016-01-07T09:00:15Z")
delayed, next RC is 12.01.2016 and the number of open issues is still growing ---
**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 8, 2016, 6:33pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/16 "2016-01-08T18:33:44Z")
The v2 milestone is now being used for thing we’ll be looking to fix in the 2.0.x series of releases, and not necessarily blockers to the 2.0.0-final release. Generally things that are marked P1/P2 in the milestone are what we want to get fixed before the final release. So we’re still on track for 1/12. ---
**Author:** ![Dan\_Swartz](https://avatars.discourse-cdn.com/v4/letter/d/439d5e/32.png) [@Dan\_Swartz](https://forum.ansible.com/u/Dan_Swartz)\ **Post date:** [January 8, 2016, 10:07pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/17 "2016-01-08T22:07:20Z")
I’m sorry, I’m not sure I understood that. Are you saying that 2.0.0-final is on track for Tuesday? ---
**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 11, 2016, 2:01am UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/18 "2016-01-11T02:01:14Z")
Yep, currently no plans to delay further. ---
**Author:** ![Jeff\_Reter](https://avatars.discourse-cdn.com/v4/letter/j/a88e4f/32.png) [@Jeff\_Reter](https://forum.ansible.com/u/Jeff_Reter)\ **Post date:** [January 11, 2016, 4:25pm UTC](https://forum.ansible.com/t/eta-on-ansible-2-0/18465/19 "2016-01-11T16:25:08Z")
[https://github.com/ansible/ansible/issues/13795](https://github.com/ansible/ansible/issues/13795) this will break things for us