From: "Alex Bennée" <alex.bennee@linaro.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Peter Maydell" <peter.maydell@linaro.org>,
"Willian Rampazzo" <wrampazz@redhat.com>,
qemu-devel@nongnu.org,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section
Date: Mon, 08 Mar 2021 11:57:28 +0000 [thread overview]
Message-ID: <878s6xam83.fsf@linaro.org> (raw)
In-Reply-To: <20210307113403.11028-1-thuth@redhat.com>
Thomas Huth <thuth@redhat.com> writes:
> The status of the gitlab-CI files is currently somewhat confusing, and
> it is often not quite clear whether a patch should go via my tree or
> via the testing tree of Alex. That situation has grown historically...
> Initially, I was the only one using the gitlab-CI, just for my private
> repository there. But in the course of time, the gitlab-CI switched to
> use the containers from tests/docker/ (which is not part of the gitlab-CI
> section in the MAINTAINERS file), and QEMU now even switched to gitlab.com
> completely for the repository and will soon use it as its gating CI, too.
> So it makes way more sense if the gitlab-ci.yml files belong to the people
> who are owning the qemu-project on gitlab.com and take care of the gitlab
> CI there. Thus let's merge the gitlab-ci section into the common "test and
> build automation" section,
I have no problem with this, might as well keep it all together.
> and change the status of myself to a "reviewer"
> there instead.
Can we not have multiple maintainers? Considering how important keeping
the testing green should be wouldn't it help to keep the bus factor
lower (not to mention holidays/breaks and just plain busy with other
things periods). It shouldn't be to hard to track as long as we mention
when we queue things to our trees?
> While we're at it, I'm also removing the line with Fam there for now,
> since he was hardly active during the last years in this area anymore.
> If he ever gets more time for this part again in the future, we surely
> can add the line back again.
>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
> MAINTAINERS | 19 ++++++-------------
> 1 file changed, 6 insertions(+), 13 deletions(-)
>
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 26c9454823..e9cd29ed0b 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -3262,17 +3262,21 @@ F: include/hw/remote/iohub.h
>
> Build and test automation
> -------------------------
> -Build and test automation
> +Build and test automation, Linux Continuous Integration
> M: Alex Bennée <alex.bennee@linaro.org>
> -M: Fam Zheng <fam@euphon.net>
> R: Philippe Mathieu-Daudé <philmd@redhat.com>
> +R: Thomas Huth <thuth@redhat.com>
> +R: Wainer dos Santos Moschetta <wainersm@redhat.com>
> S: Maintained
> F: .github/lockdown.yml
> +F: .gitlab-ci.yml
> +F: .gitlab-ci.d/
> F: .travis.yml
> F: scripts/ci/
> F: tests/docker/
> F: tests/vm/
> F: scripts/archive-source.sh
> +W: https://gitlab.com/qemu-project/qemu/pipelines
> W: https://travis-ci.org/qemu/qemu
> W: http://patchew.org/QEMU/
>
> @@ -3289,17 +3293,6 @@ S: Maintained
> F: .cirrus.yml
> W: https://cirrus-ci.com/github/qemu/qemu
>
> -GitLab Continuous Integration
> -M: Thomas Huth <thuth@redhat.com>
> -M: Philippe Mathieu-Daudé <philmd@redhat.com>
> -M: Alex Bennée <alex.bennee@linaro.org>
> -R: Wainer dos Santos Moschetta <wainersm@redhat.com>
> -S: Maintained
> -F: .gitlab-ci.yml
> -F: .gitlab-ci.d/crossbuilds.yml
> -F: .gitlab-ci.d/*py
> -F: scripts/ci/gitlab-pipeline-status
> -
> Guest Test Compilation Support
> M: Alex Bennée <alex.bennee@linaro.org>
> R: Philippe Mathieu-Daudé <f4bug@amsat.org>
--
Alex Bennée
next prev parent reply other threads:[~2021-03-08 12:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-07 11:34 [PATCH] MAINTAINERS: Merge the Gitlab-CI section into the generic CI section Thomas Huth
2021-03-08 11:57 ` Alex Bennée [this message]
2021-03-08 12:33 ` Thomas Huth
2021-03-08 15:12 ` Peter Maydell
2021-03-08 13:34 ` Philippe Mathieu-Daudé
2021-03-08 15:11 ` Thomas Huth
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=878s6xam83.fsf@linaro.org \
--to=alex.bennee@linaro.org \
--cc=f4bug@amsat.org \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=thuth@redhat.com \
--cc=wainersm@redhat.com \
--cc=wrampazz@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.