Hi all, we're happy to announce that RC1 for 2.1.2 is now available for
testing.

This release candidate fixes many bugs, including (but not limited to):

* Fixed a bug introduced by static includes in 2.1, which prevented
notifications from going to the "top level" handler name.
* Fixed a bug where a group_vars or host_vars directory in the current
working directory would be used (and would take precedence) over those in
the inventory and/or playbook directory.
* Fixed a bug which could occur when the result of an async task did not
parse as valid JSON.
* (re)-allowed the use of ansible_python_interpreter lines with more than
one argument.
* Fixed several bugs related to the creation of the implicit localhost in
inventory.
* Fixed a bug related to an unspecified number of retries when using until.
* Fixed a race-condition bug when creating temp directories before the
worker process is forked.

How do you get it?
----------------------------------------------------------------------

The tar.gz of the release can be found here:

http://releases.ansible.com/ansible/ansible-2.1.2.0-0.1.rc1.tar.gz
SHA256: 877595c6ae0f6a4cbf91d368aeb1194d8df65cbb084033b62dd163c2a24080d7

You can also test against the git repository as follows:

$ git clone https://github.com/ansible/ansible.git
$ cd ansible
$ git checkout v2.1.2.0-0.1.rc1
$ git submodule update --init

You can then source our testing script:

$ . hacking/env-setup

or you can build your own .tar.gz (output will be
dist/ansible-2.1.2.0.tar.gz):

$ make sdist

If you discover any errors, or if you see any regressions from playbooks
which work on 1.9.x and prior, please open a Github issue and be sure to
mention you're testing against this release candidate.

Thanks!

James Cammarata

Ansible Lead/Sr. Principal Software Engineer
Ansible by Red Hat
twitter: @thejimic, 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.

Reply via email to