From: Markus Armbruster <armbru@redhat.com>
To: Thomas Huth <thuth@redhat.com>
Cc: qemu-devel@nongnu.org, "Peter Maydell" <peter.maydell@linaro.org>,
"Daniel Berrange" <berrange@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Claudio Fontana" <cfontana@suse.de>,
"John Snow" <jsnow@redhat.com>,
"Alex Bennée" <alex.bennee@linaro.org>
Subject: Re: [PATCH v2] docs/about/build-platforms: Refine the distro support policy
Date: Fri, 24 Feb 2023 07:48:23 +0100 [thread overview]
Message-ID: <875ybr36fc.fsf@pond.sub.org> (raw)
In-Reply-To: <20230223193257.1068205-1-thuth@redhat.com> (Thomas Huth's message of "Thu, 23 Feb 2023 20:32:57 +0100")
Thomas Huth <thuth@redhat.com> writes:
> For long-term distributions that release a new version only very
> seldom, we limit the support to five years after the initial release.
> Otherwise, we might need to support distros like openSUSE 15 for
> up to 7 or even more years in total due to our "two more years
> after the next major release" rule, which is just way too much to
> handle in a project like QEMU that only has limited human resources.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> v2: Only limit the maximum amount of time to five years (instead of
> four years + decreasing the amount of time after the next major
> has been released)
>
> docs/about/build-platforms.rst | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/docs/about/build-platforms.rst b/docs/about/build-platforms.rst
> index 1c1e7b9e11..7ad95ae9ae 100644
> --- a/docs/about/build-platforms.rst
> +++ b/docs/about/build-platforms.rst
> @@ -67,7 +67,8 @@ Non-supported architectures may be removed in the future following the
> Linux OS, macOS, FreeBSD, NetBSD, OpenBSD
> -----------------------------------------
>
> -The project aims to support the most recent major version at all times. Support
> +The project aims to support the most recent major version at all times for
> +up to five years after its initial release. 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
I think this is a more realistic promise. We may elect to support
beyond the five year mark, if we're so inclined.
Reviewed-by: Markus Armbruster <armbru@redhat.com>
prev parent reply other threads:[~2023-02-24 6:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-23 19:32 [PATCH v2] docs/about/build-platforms: Refine the distro support policy Thomas Huth
2023-02-24 6:48 ` Markus Armbruster [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ybr36fc.fsf@pond.sub.org \
--to=armbru@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=berrange@redhat.com \
--cc=cfontana@suse.de \
--cc=jsnow@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.