Is there an estimated release date for Ansible 2.0 ?
Cheers,
J
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
Can we get an updated estimate? Even if it’s just a matter of days vs. weeks. Thanks.
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
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!
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.
Any update on ETA?
Oh come on… you’re one year ahead. Still plenty of time until early August 
(Sorry. Just. Could. Not. Resist.)
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.
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…
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
RC2 is out. How many release candidates are expected?
J
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
Any new news on this?
J
delayed,
next RC is 12.01.2016
and the number of open issues is still growing
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.
I’m sorry, I’m not sure I understood that. Are you saying that 2.0.0-final is on track for Tuesday?
Yep, currently no plans to delay further.
https://github.com/ansible/ansible/issues/13795
this will break things for us