On 08/03/2021 12.57, Alex Bennée wrote:
Thomas Huth <th...@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?
Sure, it certainly makes sense to have multiple maintainers, but I think in
this section, it might be better to also have someone who's also a
maintainer of the qemu-project at gitlab (in case there's something to
fix/setup with a custom runner for example, and to avoid wrong
expectations)? Maybe Peter finally wants to join here to get finally away
from his exclusive merge tests?
Thomas
