Ansible 1.8.4 Released

149 views
Skip to first unread message

James Cammarata

unread,
Feb 19, 2015, 1:06:48 PM2/19/15
to ansible...@googlegroups.com, ansible-...@googlegroups.com
Hi all, Ansible 1.8.4 has been released and is now available. 

This releases fixes two regressions in modules (ec2 and mount) introduced by the 1.8.3 release.

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

Walter Dolce

unread,
Feb 19, 2015, 3:59:17 PM2/19/15
to ansible...@googlegroups.com, ansible-...@googlegroups.com

Hi,
Do you also announce package availability for distros the same way as you announce these releases?

Thank you in advance. Keep up the good work.

Kind regards,
Walter

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/ansible-project/CAMFyvFjGvKiR0nFg9dio2HRbWFVsZ6xbz1N%2BcTfHEzztipZyTw%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

James Cammarata

unread,
Feb 20, 2015, 11:34:48 PM2/20/15
to ansible...@googlegroups.com, ansible-...@googlegroups.com
Hi Walter.

No, we usually do not, since each distro packages the release at their own speed and we don't keep track of them all. I know for EPEL, it's usually about 2-3 weeks for the package to make its way out of the testing branches, while for Ubuntu and others it is much sooner.

Thanks!

James Cammarata
Director, Ansible Core Engineering
github: jimi-c

Kevin Fenzi

unread,
Feb 21, 2015, 11:13:41 AM2/21/15
to ansible...@googlegroups.com
On Fri, 20 Feb 2015 22:34:27 -0600
James Cammarata <jcamm...@ansible.com> wrote:

> Hi Walter.
>
> No, we usually do not, since each distro packages the release at
> their own speed and we don't keep track of them all. I know for EPEL,
> it's usually about 2-3 weeks for the package to make its way out of
> the testing branches, while for Ubuntu and others it is much sooner.

As one of the Fedora/EPEL maintainers, FYI:

I usually see new releases pretty quicky, do a quick test/scratch build
and then go on to official builds.

* Fedora Rawhide and pre-release Branched builds are done usually
within hours of release, and appear in the next days rawhide/branched
tree.

* Fedora stable releases are also built in hours of release, but then
are submitted as updates. They usually go out to updates-testing the
next day. They have to spend 1 week in updates-testing or get +3
karma to go to updates.

* EPEL releases are also built at the same time and submitted as
updates. They usually go out to epel-testing the next day. They must
spend 2 weeks in epel-testing or get +3 karma to go to updates.

If you don't mind unsigned packages you can always get them direct from
the buildsystem after they are built:
https://koji.fedoraproject.org/koji/packageinfo?packageID=13842

You can test any of the testing updates and provide karma at:
https://admin.fedoraproject.org/updates/search/ansible

Hope that helps.

kevin

Walter Dolce

unread,
Feb 21, 2015, 1:10:34 PM2/21/15
to ansible...@googlegroups.com

Hi James,

Thanks for the useful infos! I think it's enough to have a certain degree of awareness about the various packages availability timelines ;)

Walter Dolce

unread,
Feb 21, 2015, 1:11:53 PM2/21/15
to ansible...@googlegroups.com

Just saw the reply afterwards Kevin.
Thanks a lot as well!

Kind regards,
Walter

--
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 ansible-proje...@googlegroups.com.
To post to this group, send email to ansible...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages