We discuss Linux, FreeBSD and macOS separately, and we even go as far as splitting Linux distros into short-lifetime and long-lifetime, when ultimately the same two priciples apply everywhere: we don't want to support a platform longer than its vendor does, and in cases where the vendor support is extremely long we need to have a time-based escape hatch. Signed-off-by: Andrea Bolognani <abologna@xxxxxxxxxx> --- docs/platforms.rst | 47 ++++++++++++++-------------------------------- 1 file changed, 14 insertions(+), 33 deletions(-) diff --git a/docs/platforms.rst b/docs/platforms.rst index 2845ac40ea..702d8d56d3 100644 --- a/docs/platforms.rst +++ b/docs/platforms.rst @@ -36,46 +36,27 @@ distros listed below. * `qemu on Repology`_ * `qemu-kvm on Repology`_ -Linux OS --------- - -For distributions with frequent, short-lifetime releases, the project will aim -to support all versions that are not end of life by their respective vendors. -For the purposes of identifying supported software versions, the project will -look at Fedora, Ubuntu, and openSUSE distros. Other short-lifetime distros -will be assumed to ship similar software versions. - -For distributions with long-lifetime releases, 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. For -the purposes of identifying supported software versions, the project will look -at RHEL, Debian, Ubuntu LTS, and SLES distros. Other long-lifetime distros will -be assumed to ship similar software versions. - -Windows -------- - -The project supports building with current versions of the MinGW toolchain, -hosted on Linux. - -macOS ------ +Linux, FreeBSD and macOS +------------------------ The project aims 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. +version is released or when the vendor itself drops support, whichever comes +first. -Note that to compile libvirt will require extra packages to be made available -on the macOS host. It is recommended to use `HomeBrew`_ since this is what -libvirt CI tests with, however, `MacPorts`_ is an alternative option that is -likely to work. +For the purposes of identifying supported software versions available on Linux, +the project will look at CentOS, Debian, Fedora, openSUSE, RHEL, SLES and +Ubuntu LTS. Other distros will be assumed to ship similar software versions. -FreeBSD +For FreeBSD, decisions will be made based on the contents of the ports tree; +for macOS, `HomeBrew`_ will be used, although `MacPorts`_ is expected to carry +similar versions. + +Windows ------- -The project aims 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. +The project supports building with current versions of the MinGW toolchain, +hosted on Linux. Virtualization platforms -- 2.25.4