From: Stefan Hajnoczi <stefanha@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Markus Armbruster" <armbru@redhat.com>,
"Thomas Huth" <thuth@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Paolo Bonzini" <pbonzini@redhat.com>
Subject: Re: [PATCH] docs/about: propose OS platform/arch support tiers
Date: Thu, 15 Jan 2026 17:09:35 -0500 [thread overview]
Message-ID: <20260115220935.GA674111@fedora> (raw)
In-Reply-To: <20260115180123.848640-1-berrange@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1511 bytes --]
On Thu, Jan 15, 2026 at 06:01:23PM +0000, Daniel P. Berrangé wrote:
> Informally we have approximately three groups of platforms
>
> * Tier 1: fully built and fully tested by CI. Must always be
> kept working & regressions fixed immediately
>
> * Tier 2: fully built and partially tested by CI. Should
> always be kept working & regressions fixed quickly
>
> * Tier 3: code exists but is not built or tested by CI.
> Should not be intentionally broken but not
> guaranteed to work at any time. Downstream must
> manually test, report & fix bugs.
>
> Anything else is "unclassified" and any historical code
> remnants may be removed.
>
> It is somewhat tricky to define unambiguous rules for each tier,
> but this doc takes a stab at it. We don't need to cover every
> eventuality. If we get the core points of view across, then it
> at least sets the direction for maintainers/contributors/users.
> Other aspects can be inferred with greater accuracy than today.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
>
> This came out of the discussion about recent unnoticed breakage
> in NetBSD builds and what maintainers are expected todo about
> it (if anything)
>
> https://lists.nongnu.org/archive/html/qemu-devel/2026-01/msg02543.html
>
> docs/about/build-platforms.rst | 152 +++++++++++++++++++++++++++++++++
> 1 file changed, 152 insertions(+)
Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
prev parent reply other threads:[~2026-01-15 22:10 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-15 18:01 [PATCH] docs/about: propose OS platform/arch support tiers Daniel P. Berrangé
2026-01-15 20:39 ` BALATON Zoltan
2026-01-16 10:05 ` Daniel P. Berrangé
2026-01-15 20:48 ` Pierrick Bouvier
2026-01-16 10:46 ` Daniel P. Berrangé
2026-01-16 18:01 ` Pierrick Bouvier
2026-01-15 20:56 ` Thomas Huth
2026-01-16 10:10 ` Daniel P. Berrangé
2026-01-15 22:09 ` Stefan Hajnoczi [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=20260115220935.GA674111@fedora \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.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.