* [PATCH] qemu-doc: Clarify extent of build platform support
@ 2020-02-13 8:43 Markus Armbruster
2020-02-13 9:30 ` Daniel P. Berrangé
2020-02-13 20:47 ` Eduardo Habkost
0 siblings, 2 replies; 3+ messages in thread
From: Markus Armbruster @ 2020-02-13 8:43 UTC (permalink / raw)
To: qemu-devel; +Cc: jsnow, pbonzini, berrange, ehabkost, peter.maydell
Supporting a build platform beyond its end of life makes no sense.
Spell that out just to be clear.
Signed-off-by: Markus Armbruster <armbru@redhat.com>
---
qemu-doc.texi | 9 +++++----
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/qemu-doc.texi b/qemu-doc.texi
index a1ef6b6484..33b9597b1d 100644
--- a/qemu-doc.texi
+++ b/qemu-doc.texi
@@ -2880,10 +2880,11 @@ 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.
+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.
@section Windows
--
2.21.1
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH] qemu-doc: Clarify extent of build platform support
2020-02-13 8:43 [PATCH] qemu-doc: Clarify extent of build platform support Markus Armbruster
@ 2020-02-13 9:30 ` Daniel P. Berrangé
2020-02-13 20:47 ` Eduardo Habkost
1 sibling, 0 replies; 3+ messages in thread
From: Daniel P. Berrangé @ 2020-02-13 9:30 UTC (permalink / raw)
To: Markus Armbruster; +Cc: peter.maydell, pbonzini, jsnow, qemu-devel, ehabkost
On Thu, Feb 13, 2020 at 09:43:34AM +0100, Markus Armbruster wrote:
> Supporting a build platform beyond its end of life makes no sense.
> Spell that out just to be clear.
Agreed, that matches my intention when first writing this doc.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
> ---
> qemu-doc.texi | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
Reviewed-by: Daniel P. Berrangé <berrange@redhat.com>
>
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index a1ef6b6484..33b9597b1d 100644
> --- a/qemu-doc.texi
> +++ b/qemu-doc.texi
> @@ -2880,10 +2880,11 @@ 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.
> +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.
>
> @section Windows
>
> --
> 2.21.1
>
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] 3+ messages in thread
* Re: [PATCH] qemu-doc: Clarify extent of build platform support
2020-02-13 8:43 [PATCH] qemu-doc: Clarify extent of build platform support Markus Armbruster
2020-02-13 9:30 ` Daniel P. Berrangé
@ 2020-02-13 20:47 ` Eduardo Habkost
1 sibling, 0 replies; 3+ messages in thread
From: Eduardo Habkost @ 2020-02-13 20:47 UTC (permalink / raw)
To: Markus Armbruster; +Cc: jsnow, pbonzini, berrange, qemu-devel, peter.maydell
On Thu, Feb 13, 2020 at 09:43:34AM +0100, Markus Armbruster wrote:
> Supporting a build platform beyond its end of life makes no sense.
> Spell that out just to be clear.
>
> Signed-off-by: Markus Armbruster <armbru@redhat.com>
Thanks!
Reviewed-by: Eduardo Habkost <ehabkost@redhat.com>
> ---
> qemu-doc.texi | 9 +++++----
> 1 file changed, 5 insertions(+), 4 deletions(-)
>
> diff --git a/qemu-doc.texi b/qemu-doc.texi
> index a1ef6b6484..33b9597b1d 100644
> --- a/qemu-doc.texi
> +++ b/qemu-doc.texi
> @@ -2880,10 +2880,11 @@ 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.
> +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.
>
> @section Windows
>
> --
> 2.21.1
>
--
Eduardo
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2020-02-13 20:48 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2020-02-13 8:43 [PATCH] qemu-doc: Clarify extent of build platform support Markus Armbruster
2020-02-13 9:30 ` Daniel P. Berrangé
2020-02-13 20:47 ` Eduardo Habkost
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).