Hi all, on Monday we will be switching the devel branch over to the v2 code base. As a result, all future checkouts will use the v2 codebase by default.
As we do not expect everything to work immediately for all users, we will be taking a few steps to ensure any users running from a checkout can easily revert back to the v1 code easily.
First off, all code currently in lib/ansible/ will be relocated to the v1/ directory. This directory will also have a hacking/env-setup script, so to use the old code simply source the v1/hacking/env-setup script and you’ll be using the old codebase.
In addition to this, we’ll be creating a new tag - v1_final, which will point at the SHA of devel prior to the switch. Simply checking out this tag will get you the devel branch as it exists today. This will also go for the ansible-modules-core repository, which has one minimal change to the “command” module to support the new v2 codebase (all other modules will require zero changes to work). We wil ensure the submodules for the v1/ directory point at the correct SHA for the core modules.
The v2_final branch is the feature branch currently used for all new work on 2.0, so if you’d like to give it a try just check that out this weekend and let us know if you run into any issues.
Thanks!
That is great news 
May I ask for a short feature list about things new in v2 – doesn’t need to be a doc ready form, just something so we know which features to heavily test.
Thanks & cheers,
Florian
Hi Florian, a good summary of V2 features can be found here in the presentation I gave in London earlier this year:
http://www.slideshare.net/jimi-c/whats-new-in-v2-ansiblefest-london-2015
In summary:
- Blocks (try/except style exception handling)
- Execution strategies for running tasks in different patterns
- Include + with loops again
- Improved error message reporting (show file/line for most errors)
Hi all, on Monday we will be switching the devel branch over to the v2
code base. As a result, all future checkouts will use the v2 codebase
by default.
[* snip *]
In addition to this, we'll be creating a new tag - v1_final, which
will point at the SHA of devel prior to the switch.
Is there going to be a 1.9.2 release tagged before then? (Or after, but
that seems unlikely.)
(We tend to update conservatively, are currently at 1.7.2, and have run
into a need to a version that supports Rackspace CBS volumes and
CBS-backed instances.)
-Josh (jbs@care.com)
This email is intended for the person(s) to whom it is addressed and may contain information that is PRIVILEGED or CONFIDENTIAL. Any unauthorized use, distribution, copying, or disclosure by any person other than the addressee(s) is strictly prohibited. If you have received this email in error, please notify the sender immediately by return email and delete the message and any attachments from your system.
Hi Josh, 1.9.2 is waiting on a few fixes to the new windows modules we merged in, but should be released soon. The stable-1.9 branch is already separate from the devel branch, so there is no direct dependency there. We should be able to release 1.9.2-rc2 next week.