On Thu, Apr 05, 2018 at 10:54:53AM +0100, Daniel P. Berrangé wrote: > On Tue, Apr 03, 2018 at 05:23:21PM +0200, Pavel Hrdina wrote: > > On Tue, Apr 03, 2018 at 03:56:11PM +0100, Daniel P. Berrangé wrote: > > > Describe how we decide which host platforms to support for libvirt, > > > which in turn makes it easier to decide when a platform / software > > > version can be dropped. > > > > > > Signed-off-by: Daniel P. Berrangé <berrange@xxxxxxxxxx> > > > --- > > > docs/index.html.in | 2 +- > > > docs/platforms.html.in | 74 ++++++++++++++++++++++++++++++++++++++++++++++++++ > > > 2 files changed, 75 insertions(+), 1 deletion(-) > > > create mode 100644 docs/platforms.html.in > > > > > > > + <h3>FreeBSD</h3> > > > + > > > + <p> > > > + The project will aim to support the most recent major version > > > + at all times. Support for the previous major version will > > > + be dropped 2 years after the new major version is released. > > > + </p> > > > + > > > + <h2>Virtualization platforms</h2> > > > + > > > + <p> > > > + For hypervisor drivers which execute locally (QEMU, LXC, VZ, > > > > s/ VZ,// or s/VZ/OpenVZ/ ? > > Not sure I see why you want that ? The modern VZ driver is run locally > in libvirtd, the same as QEMU, LXC, etc. Right, once I've read it again it actually make sense. I thought that it shouldn't be mentioned twice. Pavel
Attachment:
signature.asc
Description: PGP signature
-- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
