Date: Mon, 07 Dec 2015 20:37:19 -0500 From: Nikolai Lifanov <lifanov@mail.lifanov.com> To: Johannes Jost Meixner <johannes@meixner.dk> Cc: python@freebsd.org Subject: Re: Ansible 2.0 Message-ID: <d8de0385b618b922bba93b7ff704c640@mail.lifanov.com> In-Reply-To: <56660BBD.9050502@meixner.dk> References: <5665D28D.1070305@meixner.dk> <5665D92E.2000701@mail.lifanov.com> <56660BBD.9050502@meixner.dk>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-12-07 17:44, Johannes Jost Meixner wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA256 > > > > On 12/ 7/15 09:08 PM, Nikolai Lifanov wrote: >> On 12/07/15 13:40, Johannes Jost Meixner wrote: >>> Hey Nikolai, >>> >>> I've just heard that Ansible 2.0-RC2 has been released. >>> >>> Do you plan to do a port for it, or would you rather someone else >>> took that over? >>> >>> Best -Johannes >>> >> >> I plan to port Ansible 2.0 when it's released as sysutils/ansible >> and move 1.9 to sysutils/ansible1. If it's valuable to track RC >> releases, I'm not opposed to creating something like >> sysutils/ansible-devel. > > I don't think -devel will be necessary - judging from what I've heard > on #ansible (freenode) from the developer that said RC2 was ready, > they plan to release 2.0 "soon", within one or two weeks. > > Given that I've also heard that most syntax will work in 2.0 I think > your idea (ansible to get 2.x and ansible1 for 1.9.4) is reasonable. > > Best > - -Johannes > >> >> I have not tracked any RC releases in the past (1.9, 1.8, etc.). >> >> Thoughts? >> >> - Nikolai Lifanov _______________________________________________ >> freebsd-python@freebsd.org mailing list >> https://lists.freebsd.org/mailman/listinfo/freebsd-python To >> unsubscribe, send any mail to >> "freebsd-python-unsubscribe@freebsd.org" >> > > - -- > I've recently changed my email address to: > > johannes@meixner.dk > > Please update your addressbook accordingly. > > Best regards, > > Johannes Meixner > http://www.meixner.dk > Cool, thanks. I'll stick to the plan in this case. Syntax changes are significant enough to warrant ansible1 for a few months to give people lots of time to migrate. Changes from 1.8 to 1.9 or 1.7 to 1.8 were incompatible, but much more minor. I'm sympathetic to overlapping support so that people aren't forced to run unsupported software at any point in time. Another thought is, I don't trust Ansible releases to go well. I created the port circa 0.9. It's a lot better now, but before the move to Github, ansible.com/ansible.cc snapshots were being rerolled with no warning. Now I occasionally see one or two bugfix releases within 24 hours of each other. Given that it's possible to run beta/RC tags from a git checkout, tracking these has not been attractive to me. Cheers, - Nikolai Lifanov
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d8de0385b618b922bba93b7ff704c640>