On Wed, 2019-11-20 at 23:19 +0100, Fabiano Fidêncio wrote: > On Wed, Nov 20, 2019 at 10:46 PM Jim Fehlig <jfehlig@xxxxxxxx> wrote: > > On 11/20/19 2:16 PM, Fabiano Fidêncio wrote: > > > On Wed, Nov 20, 2019 at 8:44 PM Jim Fehlig <jfehlig@xxxxxxxx> wrote: > > > > 15.1 will continue to be actively supported alongside 15.2 for six months after > > > > the release of 15.2. The lifecycle is described here > > > > > > > > https://en.opensuse.org/Lifetime > > > > > > > > Perhaps it is best to just support the latest Leap release plus openSUSE > > > > Tumbleweed? I.e. I send a patch to replace the 15.1 machine with 15.2 once it is > > > > released. > > > > > > I'd adopt the same policy we have for other distros. Support the last > > > two releases (as in, Fedora 30 and Fedora 31). Unless it makes more sense to support the latest 42.x and the latest 15.x instead? But it looks like the former has been discontinued now, so perhaps just the latest 15.x and then, once that's released, the latest 16.x (guessing the version number :) in addition to that? > > > Leap seems to fit in the "Fedora" case. Thus, I'd keep 15.1, 15.2, 15.3, ... > > > > But how to name those? Is a '.' in the name problematic? Should inventory have > > libvirt-opensuse-15.1, libvirt-opensuse-15.2, etc? > > Now, knowing the release and life cycles, I'd suggest to keep it as: > libvirt-opensuse-15.1, libvirt-opensuse-15.2, and so on ... exactly as > you did in the patch you submitted. Agreed. Incidentally, once we start introducing x.y version numbers it would make sense to rename Ubuntu guests so that they look like libvirt-ubuntu-18.04 and so on. > > > Together with that, I really would like to have Tumbleweed supported as well. > > > > Nod. That one is easy to name: libvirt-opensuse-tw :-). Please just call it libvirt-opensuse-tumbleweed instead: no need to use shorthands. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
