qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
* [PATCH] docs: simplify and clarify the platform support rules
@ 2020-09-17 15:56 Daniel P. Berrangé
  2020-09-17 16:03 ` no-reply
                   ` (3 more replies)
  0 siblings, 4 replies; 6+ messages in thread
From: Daniel P. Berrangé @ 2020-09-17 15:56 UTC (permalink / raw)
  To: qemu-devel
  Cc: Peter Maydell, Thomas Huth, Daniel P. Berrangé,
	Eduardo Habkost, Markus Armbruster

The distinction between short life and long life Linux distributions
turned out to be redundant. They can both be covered in a simple way
by noting support will target the current release, and the previous
release for a period of two years or until its EOL. This rule can also
apply to the other UNIX based distros, leaving only Windows needing a
different set of rules.

This also clarifies that Debian LTS is out of scope, because the LTS
support is provided by a separate group from the main Debian maintainer
team.

Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
---

This is a spin off from the Python 3.5 thread

https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06358.html

 docs/system/build-platforms.rst | 59 ++++++++++-----------------------
 1 file changed, 18 insertions(+), 41 deletions(-)

diff --git a/docs/system/build-platforms.rst b/docs/system/build-platforms.rst
index 9734eba2f1..03d2fd217f 100644
--- a/docs/system/build-platforms.rst
+++ b/docs/system/build-platforms.rst
@@ -29,51 +29,28 @@ The Repology site https://repology.org is a useful resource to identify
 currently shipped versions of software in various operating systems,
 though it does not cover all distros listed below.
 
-Linux OS
---------
+Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
+-----------------------------------------
 
-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.
+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 or when the vendor itself drops support, whichever comes
+first. In this context, third-party efforts to extend the lifetime of a distro
+are not considered, even when they are endorsed by the vendor (eg. Debian LTS).
 
-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, or when it reaches "end of life". 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.
+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.
 
-Windows
--------
-
-The project supports building with current versions of the MinGW
-toolchain, hosted on Linux.
-
-macOS
------
-
-The project supports building with the two most recent versions of
-macOS, with the current Homebrew package set available.
+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.
 
-FreeBSD
+Windows
 -------
 
-The project aims to support all versions which are not end of
-life.
-
-NetBSD
-------
-
-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.
-
-OpenBSD
--------
+The project supports building with current versions of the MinGW toolchain,
+hosted on Linux (Debian/Fedora).
 
-The project aims to support all versions which are not end of
-life.
+The version of the Windows API that's currently targeted is Vista / Server
+2008.
-- 
2.26.2



^ permalink raw reply related	[flat|nested] 6+ messages in thread

* Re: [PATCH] docs: simplify and clarify the platform support rules
  2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
@ 2020-09-17 16:03 ` no-reply
  2020-09-17 16:15 ` Thomas Huth
                   ` (2 subsequent siblings)
  3 siblings, 0 replies; 6+ messages in thread
From: no-reply @ 2020-09-17 16:03 UTC (permalink / raw)
  To: berrange; +Cc: peter.maydell, thuth, berrange, ehabkost, qemu-devel, armbru

Patchew URL: https://patchew.org/QEMU/20200917155606.1623795-1-berrange@redhat.com/



Hi,

This series failed build test on FreeBSD host. Please find the details below.






The full log is available at
http://patchew.org/logs/20200917155606.1623795-1-berrange@redhat.com/testing.FreeBSD/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] docs: simplify and clarify the platform support rules
  2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
  2020-09-17 16:03 ` no-reply
@ 2020-09-17 16:15 ` Thomas Huth
  2020-09-17 16:24 ` no-reply
  2020-09-17 16:28 ` Eduardo Habkost
  3 siblings, 0 replies; 6+ messages in thread
From: Thomas Huth @ 2020-09-17 16:15 UTC (permalink / raw)
  To: Daniel P. Berrangé, qemu-devel
  Cc: Peter Maydell, Eduardo Habkost, Markus Armbruster

On 17/09/2020 17.56, Daniel P. Berrangé wrote:
> The distinction between short life and long life Linux distributions
> turned out to be redundant. They can both be covered in a simple way
> by noting support will target the current release, and the previous
> release for a period of two years or until its EOL. This rule can also
> apply to the other UNIX based distros, leaving only Windows needing a
> different set of rules.
> 
> This also clarifies that Debian LTS is out of scope, because the LTS
> support is provided by a separate group from the main Debian maintainer
> team.
> 
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> 
> This is a spin off from the Python 3.5 thread
> 
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06358.html
> 
>  docs/system/build-platforms.rst | 59 ++++++++++-----------------------
>  1 file changed, 18 insertions(+), 41 deletions(-)
> 
> diff --git a/docs/system/build-platforms.rst b/docs/system/build-platforms.rst
> index 9734eba2f1..03d2fd217f 100644
> --- a/docs/system/build-platforms.rst
> +++ b/docs/system/build-platforms.rst
> @@ -29,51 +29,28 @@ The Repology site https://repology.org is a useful resource to identify
>  currently shipped versions of software in various operating systems,
>  though it does not cover all distros listed below.
>  
> -Linux OS
> ---------
> +Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> +-----------------------------------------
>  
> -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.
> +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

I hope it is clear that for Ubuntu, major version means LTS and not each
and every bi-annual release?

> +version is released or when the vendor itself drops support, whichever comes
> +first. In this context, third-party efforts to extend the lifetime of a distro
> +are not considered, even when they are endorsed by the vendor (eg. Debian LTS).
>  
> -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, or when it reaches "end of life". 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.
> +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.

Ok, here you explicitly state Ubuntu LTS, so I think it should be clear.

> -Windows
> --------
> -
> -The project supports building with current versions of the MinGW
> -toolchain, hosted on Linux.
> -
> -macOS
> ------
> -
> -The project supports building with the two most recent versions of
> -macOS, with the current Homebrew package set available.
> +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.
>  
> -FreeBSD
> +Windows
>  -------
>  
> -The project aims to support all versions which are not end of
> -life.
> -
> -NetBSD
> -------
> -
> -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.
> -
> -OpenBSD
> --------
> +The project supports building with current versions of the MinGW toolchain,
> +hosted on Linux (Debian/Fedora).
>  
> -The project aims to support all versions which are not end of
> -life.
> +The version of the Windows API that's currently targeted is Vista / Server
> +2008.
> 

Sounds good to me.

Acked-by: Thomas Huth <thuth@redhat.com>



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] docs: simplify and clarify the platform support rules
  2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
  2020-09-17 16:03 ` no-reply
  2020-09-17 16:15 ` Thomas Huth
@ 2020-09-17 16:24 ` no-reply
  2020-09-17 16:28 ` Eduardo Habkost
  3 siblings, 0 replies; 6+ messages in thread
From: no-reply @ 2020-09-17 16:24 UTC (permalink / raw)
  To: berrange; +Cc: peter.maydell, thuth, berrange, ehabkost, qemu-devel, armbru

Patchew URL: https://patchew.org/QEMU/20200917155606.1623795-1-berrange@redhat.com/



Hi,

This series seems to have some coding style problems. See output below for
more information:

N/A. Internal error while reading log file



The full log is available at
http://patchew.org/logs/20200917155606.1623795-1-berrange@redhat.com/testing.checkpatch/?type=message.
---
Email generated automatically by Patchew [https://patchew.org/].
Please send your feedback to patchew-devel@redhat.com

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] docs: simplify and clarify the platform support rules
  2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
                   ` (2 preceding siblings ...)
  2020-09-17 16:24 ` no-reply
@ 2020-09-17 16:28 ` Eduardo Habkost
  2020-09-17 16:34   ` Daniel P. Berrangé
  3 siblings, 1 reply; 6+ messages in thread
From: Eduardo Habkost @ 2020-09-17 16:28 UTC (permalink / raw)
  To: Daniel P. Berrangé
  Cc: Peter Maydell, Thomas Huth, qemu-devel, Markus Armbruster

On Thu, Sep 17, 2020 at 04:56:06PM +0100, Daniel P. Berrangé wrote:
> The distinction between short life and long life Linux distributions
> turned out to be redundant. They can both be covered in a simple way
> by noting support will target the current release, and the previous
> release for a period of two years or until its EOL. This rule can also
> apply to the other UNIX based distros, leaving only Windows needing a
> different set of rules.
> 
> This also clarifies that Debian LTS is out of scope, because the LTS
> support is provided by a separate group from the main Debian maintainer
> team.
> 
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> 
> This is a spin off from the Python 3.5 thread
> 
> https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06358.html
> 
>  docs/system/build-platforms.rst | 59 ++++++++++-----------------------
>  1 file changed, 18 insertions(+), 41 deletions(-)
> 
> diff --git a/docs/system/build-platforms.rst b/docs/system/build-platforms.rst
> index 9734eba2f1..03d2fd217f 100644
> --- a/docs/system/build-platforms.rst
> +++ b/docs/system/build-platforms.rst
> @@ -29,51 +29,28 @@ The Repology site https://repology.org is a useful resource to identify
[...]
> +Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> +-----------------------------------------
[...]
> +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.

Shouldn't we mention NetBSD and OpenBSD too?

-- 
Eduardo



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: [PATCH] docs: simplify and clarify the platform support rules
  2020-09-17 16:28 ` Eduardo Habkost
@ 2020-09-17 16:34   ` Daniel P. Berrangé
  0 siblings, 0 replies; 6+ messages in thread
From: Daniel P. Berrangé @ 2020-09-17 16:34 UTC (permalink / raw)
  To: Eduardo Habkost; +Cc: Peter Maydell, Thomas Huth, qemu-devel, Markus Armbruster

On Thu, Sep 17, 2020 at 12:28:51PM -0400, Eduardo Habkost wrote:
> On Thu, Sep 17, 2020 at 04:56:06PM +0100, Daniel P. Berrangé wrote:
> > The distinction between short life and long life Linux distributions
> > turned out to be redundant. They can both be covered in a simple way
> > by noting support will target the current release, and the previous
> > release for a period of two years or until its EOL. This rule can also
> > apply to the other UNIX based distros, leaving only Windows needing a
> > different set of rules.
> > 
> > This also clarifies that Debian LTS is out of scope, because the LTS
> > support is provided by a separate group from the main Debian maintainer
> > team.
> > 
> > Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> > ---
> > 
> > This is a spin off from the Python 3.5 thread
> > 
> > https://lists.gnu.org/archive/html/qemu-devel/2020-09/msg06358.html
> > 
> >  docs/system/build-platforms.rst | 59 ++++++++++-----------------------
> >  1 file changed, 18 insertions(+), 41 deletions(-)
> > 
> > diff --git a/docs/system/build-platforms.rst b/docs/system/build-platforms.rst
> > index 9734eba2f1..03d2fd217f 100644
> > --- a/docs/system/build-platforms.rst
> > +++ b/docs/system/build-platforms.rst
> > @@ -29,51 +29,28 @@ The Repology site https://repology.org is a useful resource to identify
> [...]
> > +Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> > +-----------------------------------------
> [...]
> > +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.
> 
> Shouldn't we mention NetBSD and OpenBSD too?

Hmm, yes, i updated the section heading but not the text

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 :|



^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2020-09-17 16:44 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2020-09-17 15:56 [PATCH] docs: simplify and clarify the platform support rules Daniel P. Berrangé
2020-09-17 16:03 ` no-reply
2020-09-17 16:15 ` Thomas Huth
2020-09-17 16:24 ` no-reply
2020-09-17 16:28 ` Eduardo Habkost
2020-09-17 16:34   ` Daniel P. Berrangé

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).