I would also recommend creating a new thread on ansible-project with any problems you are having.
Generally speaking, 2.0 should be backwards compatible, and if you are having issues with a playbook that ran fine, we should probably know a little more about it to determine if it is an issue with the 2.0 code base. On Friday, November 20, 2015, Brian Coca <[email protected]> wrote: > The changelog has most of the things you need to look at > https://github.com/ansible/ansible/blob/stable-2.0/CHANGELOG.md > > Variable scope has not changed, precedence has been clarified and > templating has been defered to the last possible moment. > These last 2 have made it possible to fix many silent errors, which > are now shown when they were ignored before. > > -- > Brian Coca > > -- > 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] <javascript:;>. > To post to this group, send email to [email protected] > <javascript:;>. > To view this discussion on the web visit > https://groups.google.com/d/msgid/ansible-project/CAJ5XC8mmWfqocDHEQ%2BJaTwMMYabooJ5WcV9obTa1wz%2BiKLEzPQ%40mail.gmail.com > . > For more options, visit https://groups.google.com/d/optout. > -- Matt Martz @sivel sivel.net -- 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/CAD8N0v9zMQJ368KuXeu-O%3Dkb-H3aiy2_jdTnEOrMYw_V6V7hRA%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
