Hey all,

We've encountered one regression in 1.8.3 that we'd like to put out a
1.8.4 release to address:
https://github.com/ansible/ansible-modules-core/issues/808

If any of you have encountered something that worked in 1.8.2 and
regressed in 1.8.3 that you
think should get fixed let us know ASAP and we'll see if we can squeeze it in.

Please restrict yourselves to regressions.  Our hope is that
restricting 1.8.4 to regression
fixes will add polish to 1.8 with less risk of introducing new bugs.
1.9 isn't too far away
and we want to land non-regressions there.

Thanks,
-Toshio


On Tue, Feb 17, 2015 at 3:22 PM, James Cammarata <[email protected]> wrote:
> Hi all, Ansible 1.8.3 has been released and is now available.
>
> This releases fixes one security bug (temp files created when using
> "ansible-vault view <filename>" are not created with a secure umask), as
> well as including fixes for many minor bugs with the core code and modules
> which are already in devel. If you use the ansible-vault command, we
> recommend users upgrade as soon as possible.
>
> Thanks to Nicolas Le Manchet for discovering and reporting the security
> issue to us!
>
> This update is available via PyPi and releases.ansible.com now, and packages
> for distros will be available as soon as possible.
>
> Thanks!
>
> James Cammarata
> Director, Ansible Core Engineering
> github: jimi-c
>
> --
> You received this message because you are subscribed to the Google Groups
> "Ansible Announcements" 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/CAG9juEqy-F2bpE4_4gvFwgCz-CJmbmTDR62UxqQ-a03FTREhfA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to