Hi all, we're happy to announce that Beta1 for 2.4.2 is now available for testing.
How do you get it? ---------------------------------------------------------------------- The tar.gz of the release can be found here: https://releases.ansible.com/ansible/ansible-2.4.2.0-0.1.beta1.tar.gz SHA256: 7f1d76cbfcc47f7d219e3f861d861b00ba7bee5651c3b5c458a53974f8f7896a You can also test against the git repository as follows: $ git clone https://github.com/ansible/ansible.git $ cd ansible $ git checkout v2.4.2.0-0.1.beta1 You can then source our testing script: $ . hacking/env-setup or you can build your own .tar.gz (output will be dist/ansible-2.4.2.0.tar.gz): $ make sdist If you discover any errors, or if you see any regressions from playbooks which work on 2.4.1 and prior, please open a Github issue and be sure to mention you're testing against this release candidate. ---------------------------------------------------------------------- Q: But 2.4.1 just came out yesterday. Why a new tarball today? A: For the 2.4 release series we're trying to make a bugfix release approximately once per month. Our hope is that once per month is quick enough that people don't feel that they are waiting for a huge amount of time for a bugfix release which addresses their set of issues but long enough that people won't feel they are upgrading every single day. In order to hit the once per month cadence, we have to be disciplined during the release candidates and only take bugs that are either addressing blockers or very low risk. This means that bugfixes which aren't blockers and could have unintended side-effects are pushed to the next release cycle. We know that can be frustrating, especially when a bug missed being in the previous rc by just a few days. So today I've been merging the fixes that accumulated over the past few weeks of waiting for the release candidate to turn into final and put them into a beta tarball for everyone to start testing and finding the blocker bugs early so that we can have a solid 2.4.2 release. Thanks for testing! Toshio Kuratomi -- 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 ansible-devel+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
