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) James Cammarata Director, Ansible Core Engineering github: jimi-c On Sat, May 30, 2015 at 4:27 PM, Florian Apolloner <[email protected]> wrote: > 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 > > > On Saturday, May 30, 2015 at 12:05:52 AM UTC+1, James Cammarata wrote: >> >> 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! >> >> James Cammarata >> Director, Ansible Core Engineering >> github: jimi-c >> > -- > You received this message because you are subscribed to the Google Groups > "Ansible Development" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Ansible Project" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMFyvFgVkBjB23C-dmvFbsqNmVnHe3r%3DOXSMhjR3unoj7L_pRg%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
