From: "Alex Bennée" <alex.bennee@linaro.org>
To: Andrea Bolognani <abologna@redhat.com>
Cc: "Thomas Huth" <thuth@redhat.com>,
"Daniel P . Berrangé" <berrange@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH 2/2] tests: Update CentOS 8 container to CentOS Stream 8
Date: Tue, 01 Feb 2022 17:35:44 +0000 [thread overview]
Message-ID: <87k0eexze4.fsf@linaro.org> (raw)
In-Reply-To: <CABJz62Osah308O2pHFMWs+D2X+Mq=aOf1NAKFcUaWF5bGzwJEw@mail.gmail.com>
Andrea Bolognani <abologna@redhat.com> writes:
> On Tue, Feb 01, 2022 at 11:19:11AM +0100, Thomas Huth wrote:
>> +++ b/tests/docker/dockerfiles/centos8.docker
>> @@ -1,10 +1,10 @@
>> # THIS FILE WAS AUTO-GENERATED
>> #
>> -# $ lcitool dockerfile centos-8 qemu
>> +# $ lcitool dockerfile centos-stream-8 qemu
>> #
>> # https://gitlab.com/libvirt/libvirt-ci
>>
>> -FROM docker.io/library/centos:8
>> +FROM quay.io/centos/centos:stream8
> [...]
>> +++ b/tests/lcitool/refresh
>> @@ -77,7 +77,7 @@ ubuntu2004_tsanhack = [
>> ]
>>
>> try:
>> - generate_dockerfile("centos8", "centos-8")
>> + generate_dockerfile("centos8", "centos-stream-8")
>
> I'm not convinced this is a good idea.
>
> CentOS 8 and CentOS Stream 8 are two pretty distinct operating
> systems in terms of update cadence and stability expectations, so I
> think that using the label "centos8" for containers and CI jobs that
> are actually consuming CentOS Stream 8 is going to be a source of
> confusion.
>
> I recommend proceeding with a thorough rename, after which the string
> "centos8" no longer shows up anywhere, instead.
Thomas do you agree? Should I drop the patch in favour or a new version
with a more extensive rename?
--
Alex Bennée
next prev parent reply other threads:[~2022-02-01 22:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-01 10:19 [PATCH 2/2] tests: Update CentOS 8 container to CentOS Stream 8 Thomas Huth
2022-02-01 10:53 ` Thomas Huth
2022-02-01 11:01 ` Philippe Mathieu-Daudé via
2022-02-01 11:15 ` Alex Bennée
2022-02-01 17:08 ` Andrea Bolognani
2022-02-01 17:35 ` Alex Bennée [this message]
2022-02-01 17:47 ` Philippe Mathieu-Daudé via
2022-02-01 18:34 ` Andrea Bolognani
2022-02-02 5:36 ` Thomas Huth
2022-02-01 18:02 ` Daniel P. Berrangé
2022-02-01 18:29 ` Andrea Bolognani
2022-02-03 17:39 ` Alex Bennée
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=87k0eexze4.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=abologna@redhat.com \
--cc=berrange@redhat.com \
--cc=bleal@redhat.com \
--cc=f4bug@amsat.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@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.