Unofficial rpms of 2.0.1rc1  for Fedora and EPEL (CentOS/RHEL/etc) are
now available in this copr repository:
https://copr.fedorainfracloud.org/coprs/toshio/ansible-upstream/

-Toshio

On Thu, Jan 28, 2016 at 1:52 PM, James Cammarata <[email protected]> wrote:
> Hi all, we're happy to announce the RC1 release candidate for Ansible 2.0.1!
>
> This release candidate includes many bug fixes since the 2.0 release:
>
> * Fixes a major compatibility break in the synchronize module shipped with
>   2.0.0.x.  That version of synchronize ran sudo on the controller prior to
>   running rsync.  In 1.9.x and previous, sudo was run on the host that rsync
>   connected to.  2.0.1 restores the 1.9.x behaviour.
> * Additionally, several other problems with where synchronize chose to run
> when
>   combined with delegate_to were fixed.  In particular, if a playbook
> targetted
>   localhost and then delegated_to a remote host the prior behavior (in 1.9.x
>   and 2.0.0.x) was to copy files between the src and destination directories
> on
>   the delegated host.  This has now been fixed to copy between localhost and
>   the delegated host.
> * Fix a regression where synchronize was unable to deal with unicode paths.
> * Fix a regression where synchronize deals with inventory hosts that use
>   localhost but with an alternate port.
> * Fixes a regression where the retry files feature was not implemented.
> * Fixes a regression where the any_errors_fatal option was implemented in
> 2.0
>   incorrectly, and also adds a feature where any_errors_fatal can be set at
>   the block level.
> * Fix tracebacks when playbooks or ansible itself were located in
> directories
>   with unicode characters.
> * Fix bug when sending unicode characters to an external pager for display.
> * Fix a bug with squashing loops for special modules (mostly package
> managers).
>   The optimization was squashing when the loop did not apply to the
> selection
>   of packages.  This has now been fixed.
> * Temp files created when using vault are now "shredded" using the unix
> shred
>   program which overwrites the file with random data.
> * Some fixes to cloudstack modules for case sensitivity
> * Fix non-newstyle modules (non-python modules and old-style modules) to
>   disabled pipelining.
> * Fix fetch module failing even if fail_on_missing is set to False
> * Fix for cornercase when local connections, sudo, and raw were used
> together.
>
>
> How do you get it?
> ----------------------------------------------------------------------
>
> The tar.gz of the release can be found here:
>
> http://releases.ansible.com/ansible/ansible-2.0.1.0-0.1.rc1.tar.gz
> SHA256: ab2230f22d742e1379c72a3a59b18779a6aad2b4db69e87e073478028f51b24b
>
> You can also test against the git repository as follows:
>
> $ git clone https://github.com/ansible/ansible.git
> $ cd ansible
> $ git checkout v2.0.1.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.0.1.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 Project Lead
> 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.

-- 
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/CAG9juEpSeKfpXv2480Lud-6pgVd6xN9MM-tW8qwjo5hDBfgf6A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to