[00:01] <kpcyrd> nacc: https://github.com/cloud-init/cloud-init/releases
[00:01] <powersj> kpcyrd: here is where we changed the version schema: https://lists.launchpad.net/cloud-init/msg00097.html
[00:01] <powersj> basically we follow a YY.release method now
[00:01] <powersj> That means 18.1 will be next up
[00:02] <powersj> As far as those releases/tags that are showing up in GitHub, every time we make a release to the development release I beleive a tag gets made, similarly when we make an SRU to 16.04 and 17.10.
[00:03] <nacc> i would assume hte ubuntu/ namespace is for uploads to ubuntu as well
[00:03] <nacc> but not sure
[00:03] <kpcyrd> powersj: I see. So https://github.com/cloud-init/cloud-init/releases/tag/17.2 is the latest "portable" release for now (ignoring everything with ubuntu)?
[00:05] <kpcyrd> context: I was about to use cloud-init on archlinux and noticed the package was moved back into AUR and up for adoption, so I'm currently trying to get it back on track
[00:05] <powersj> kpcyrd: I'd prefer smoser or blackboxsw answer that one, but my understanding is even the latest tag should be useable, it will just have additional fixes and changes since 17.2
[00:05] <powersj> ah cool!
[00:06] <powersj> kpcyrd: smoser usually comes back in in a few hours to see if anything needs his attention
[00:07] <powersj> fwiw here is the 17.2 announcement https://lists.launchpad.net/cloud-init/msg00117.html
[00:31] <kpcyrd> nice! I think I have to do some testing before I upload a new version anyway, feel free to ping me
[01:58] <smoser> kpcyrd: for sure 17.2 is latest "stable" release.  the ubuntu tags are just things that have been uploaded to  ubuntu.
[01:58] <smoser> we generally strive for "always releasable trunk".
[01:59] <smoser> we expect to have 18.1 next thursday (Feb 22)
[01:59] <smoser> if you find things quickly that are blockers for you we can get them in.
[09:31] <kpcyrd> smoser: there have been a few bugreports (see comment section https://aur.archlinux.org/packages/cloud-init/), I think most of them are resolved by bumping the version
[09:32] <kpcyrd> the package currently also explicitly sets python2, but the code reads like python3 is supported, so I would try to change that as well
[11:28] <catmando> hey all
[11:28] <catmando> i've got a couple of problems
[11:29] <catmando> 1: cloud-init keeps resetting my hostname to localhost even though i've set preserve_hostname: False and hostname: some_hostname
[14:09] <smoser> kpcyrd: yes, python3 is supported, that is what is used on ubuntu. you should move that.