qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>,
	"Michael Tokarev" <mjt@tls.msk.ru>
Cc: "Alex Bennée" <alex.bennee@linaro.org>,
	"Philippe Mathieu-Daudé" <philmd@linaro.org>,
	"Eric Blake" <eblake@redhat.com>,
	"Vladimir Sementsov-Ogievskiy" <vsementsov@yandex-team.ru>,
	"Peter Lieven" <pl@kamp.de>,
	"Richard W.M. Jones" <rjones@redhat.com>,
	"Paolo Bonzini" <pbonzini@redhat.com>,
	qemu-devel@nongnu.org, "Kevin Wolf" <kwolf@redhat.com>,
	"Hanna Reitz" <hreitz@redhat.com>,
	"Konstantin Kostiuk" <kkostiuk@redhat.com>,
	qemu-block@nongnu.org
Subject: Re: [PATCH v2 04/13] tests: Update our CI to use CentOS Stream 9 instead of 8
Date: Thu, 18 Apr 2024 08:19:13 +0200	[thread overview]
Message-ID: <d2daac8b-0a89-423b-9bf3-6ec93af04c3c@redhat.com> (raw)
In-Reply-To: <Zh_1l1v13QG6fNF3@redhat.com>

On 17/04/2024 18.15, Daniel P. Berrangé wrote:
> On Fri, Apr 12, 2024 at 03:24:06PM +0200, Thomas Huth wrote:
>> RHEL 9 (and thus also the derivatives) are available since two years
>> now, so according to QEMU's support policy, we can drop the active
>> support for the previous major version 8 now.
>> Thus upgrade our CentOS Stream container to major version 9 now.
> 
> The second reason for doing this is that Centos Stream 8
> will go EOL in about 1 month:
> 
> https://blog.centos.org/2023/04/end-dates-are-coming-for-centos-stream-8-and-centos-linux-7/
> 
>    "After May 31, 2024, CentOS Stream 8 will be archived
>     and no further updates will be provided."
> 
> I'm seeking confirmation, but I suspect after that date we
> will be unable to build centos8 containers, as the package
> repos will likely be archived.
> 
> RHEL-8 and other derivatives (Alma Linux, Rocky Linux,
> etc) remain actively supported by their respective vendors
> / communities. Only CentOS Stream EOLs.
> 
> 
> This has implications for our CI on stable branches. It is
> valid for our stable branches to continue targetting the
> RHEL-8 family of distros, as a 2 year cutoff in our support
> policy is evaluated at time of each given major release.
> 
> IOW, cherry-picking this change to switch to CentOS Stream
> 9 is possibly inappropriate for stable branches.
> 
> lcitool supports Alma Linux as target, so we could switch
> stable branches to Alma Linux 8 if desired to keep CI
> coverage of RHEL-8 family.
> 
> Thoughts ?

Either use AlmaLinux for the stable branches, or drop the EL 8 testing in 
the stable CI completely ... I assume that the probability will be rather 
low that we break something there by backporting some few patches (and if 
so, people can still complain by opening a bug ticket, then we can fix it in 
the following stable release).

  Thomas



  reply	other threads:[~2024-04-18  6:20 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-12 13:24 [PATCH v2 00/13] Drop old distros, bump glib and switch to glib URI parsing code Thomas Huth
2024-04-12 13:24 ` [PATCH v2 01/13] tests: Remove Ubuntu 20.04 container Thomas Huth
2024-04-12 17:18   ` Philippe Mathieu-Daudé
2024-04-12 13:24 ` [PATCH v2 02/13] tests/lcitool/libvirt-ci: Update to the latest master branch Thomas Huth
2024-04-15 17:09   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 03/13] tests/docker/dockerfiles: Run lcitool-refresh after the lcitool update Thomas Huth
2024-04-15 17:11   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 04/13] tests: Update our CI to use CentOS Stream 9 instead of 8 Thomas Huth
2024-04-15 17:12   ` Daniel P. Berrangé
2024-04-17 16:15   ` Daniel P. Berrangé
2024-04-18  6:19     ` Thomas Huth [this message]
2024-04-12 13:24 ` [PATCH v2 05/13] .travis.yml: Update the jobs to Ubuntu 22.04 Thomas Huth
2024-04-15 17:13   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 06/13] ci: move external build environment setups to CentOS Stream 9 Thomas Huth
2024-04-15 17:15   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 07/13] Bump minimum glib version to v2.66 Thomas Huth
2024-04-15 17:16   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 08/13] Remove glib compatibility code that is not required anymore Thomas Huth
2024-04-15 17:16   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 09/13] block/gluster: Use URI parsing code from glib Thomas Huth
2024-04-12 14:40   ` Eric Blake
2024-04-12 14:43     ` Eric Blake
2024-04-15 17:23     ` Daniel P. Berrangé
2024-04-18  6:13     ` Thomas Huth
2024-04-15 17:19   ` Daniel P. Berrangé
2024-04-12 13:24 ` [PATCH v2 10/13] block/nbd: " Thomas Huth
2024-04-12 14:45   ` Eric Blake
2024-04-12 13:24 ` [PATCH v2 11/13] block/nfs: " Thomas Huth
2024-04-12 14:49   ` Eric Blake
2024-04-12 13:24 ` [PATCH v2 12/13] block/ssh: " Thomas Huth
2024-04-12 14:56   ` Eric Blake
2024-04-12 17:04     ` Markus Armbruster
2024-04-12 13:24 ` [PATCH v2 13/13] util/uri: Remove the old URI parsing code Thomas Huth
2024-04-12 14:59   ` Eric Blake

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=d2daac8b-0a89-423b-9bf3-6ec93af04c3c@redhat.com \
    --to=thuth@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=berrange@redhat.com \
    --cc=eblake@redhat.com \
    --cc=hreitz@redhat.com \
    --cc=kkostiuk@redhat.com \
    --cc=kwolf@redhat.com \
    --cc=mjt@tls.msk.ru \
    --cc=pbonzini@redhat.com \
    --cc=philmd@linaro.org \
    --cc=pl@kamp.de \
    --cc=qemu-block@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=rjones@redhat.com \
    --cc=vsementsov@yandex-team.ru \
    /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 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).