On Fri, 2018-04-06 at 14:43 +0100, Daniel P. Berrangé wrote: > > > It just occurred to me that libvirt.org is running on CentOS 6, and we > > > rely on being able to run configure, make & make dist there, so that > > > we can do things like publish the website, create nightly snapshots, > > > etc. So even if we don't support /running/ libvirt on CentOS 6, we'll > > > need to make sure we can at least do minimal builds - doesn't need > > > hypervisors enabled, as long as make dist still works. So I think it > > > is probably worth keeping at least the core libvirt build on CentOS 6 > > > CI, even if we turn off the sub-project like language bindings. > > > > Alternatively, we can upgrade libvirt.org to centos 7. > > Not something I would do myself - would have to be DV who decides to > do that.
Seems to me like that's the way to go. I don't think we want to have any ifs or buts in our support matrix: it should be very clear-cut in order to preserve our sanity, and also to ensure people looking at the project from outside don't get confused by mixed signals. If DV doesn't have time to take care of upgrading but also doesn't have a problem with the idea, I wouldn't mind looking into it myself. -- Andrea Bolognani / Red Hat / Virtualization -- libvir-list mailing list firstname.lastname@example.org https://www.redhat.com/mailman/listinfo/libvir-list