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. > > > + libxl, etc), the set of supported operating system platforms > > + listed above will inform choices as to the minimum required > > + versions of 3rd party libraries and hypervisor management APIs. > > + If a hypervisor is not commonly shipped directly by any distro > > + listed above, (VMWare ESX, HyperV, VZ), the project aims to > > + support versions upto 5 years, or until the vendor discontinues > > + support, whichever comes first. > > + </p> > > + > > + </body> > > +</html> > > -- > > 2.14.3 > > Reviewed-by: Pavel Hrdina <phrdina@xxxxxxxxxx> Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :| -- libvir-list mailing list libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list
