Accidentally sent this off list, so let's try again...
Unrelated, but should the new escalation code really be included in 1.9?
I'd think for something with such potentially impactful changes that it
should bake for longer than an RC before release.
On Wednesday, March 11, 2015, Serge van
Hi Matt,
We had a lot of requests for pbrun support from some users and customers,
and Brian had already done a lot of work on it for the 1.9 release before
we had originally changed course and decided to make it a 2.0
feature. However, we decided to make it a stretch goal for 1.9, so users
who
On 11 March 2015 at 00:08, James Cammarata jcammar...@ansible.com wrote:
$ git checkout v1.9.0-0.1.rc1
$ . hacking/env-setup
After which time you can run ansible and ansible-playbook like normal. If
you're not familiar with the hacking/env-setup script, please refer to the
documentation
No, we noticed that too, but decided to go ahead with the release candidate
as we weren't sure if it was simply something that needed to be adjusted in
the test due to the PBRun-related changes.
If it's simply test related, we'll put the fix in the final release or the
next RC so it tests
