So, I also talked with upstream here... and they didn't seem in favor
of obsoleting either. It's just another annoyance for someone stuck
with 1.9 for whatever good or bad reason.
I suspect (but have no way of knowing) that there really are not too
many 1.9 users anyhow. It would have taken them
I am -1 to obsoleting from the experience of what happened in the past
with other deployment or configuration management systems do that. It
will break large systems and it will break small systems and it won't
'fix' any systems that anyone will tell you about.
So after an update all anyone will s
On 13 Jan 2017 11:59 pm, "Kevin Fenzi" wrote:
On Fri, 13 Jan 2017 00:18:09 +
Peter Robinson wrote:
> On Thu, Jan 12, 2017 at 8:44 PM, Kevin Fenzi wrote:
> > Greetings.
> >
> > When ansible 2.0 was released there were some changes in playbook
> > handling made. For this reason, we created a
On Fri, 13 Jan 2017 00:18:09 +
Peter Robinson wrote:
> On Thu, Jan 12, 2017 at 8:44 PM, Kevin Fenzi wrote:
> > Greetings.
> >
> > When ansible 2.0 was released there were some changes in playbook
> > handling made. For this reason, we created a backwards compatible
> > package with ansible 1
On Thu, Jan 12, 2017 at 8:44 PM, Kevin Fenzi wrote:
> Greetings.
>
> When ansible 2.0 was released there were some changes in playbook
> handling made. For this reason, we created a backwards compatible
> package with ansible 1.9 to ease the transition for those that needed
> more time to adjust t
