public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Non-maintainer commits and CI
Date: Mon, 1 Mar 2021 14:24:41 +0000	[thread overview]
Message-ID: <6B266338-EBBC-46A0-A63F-DA1DD1AB582B@gentoo.org> (raw)
In-Reply-To: <3519644.MHq7AAxBmi@spectre>

[-- Attachment #1: Type: text/plain, Size: 876 bytes --]


> On 7 Jan 2021, at 14:28, Agostino Sarubbo <ago@gentoo.org> wrote:
> 
> Hello,
> 
> it happens frequently that CI discovers failure(s) in non-maintainer commits.
> 
> The most striking examples are maintainer-needed, proxy-maint and general pull
> request where who made the change has no visibility on the new bug.
> 
> Do you think that is a good idea to CC everyone involved in the commit?
> 

Hi all,

Following up on this, ago has implemented this after I brought it up to him - thank you ago!

The committer will be CCed on bugs and upon requests this can be disabled where maintainer is a member
of a project alias (to avoid receive mail from both herd and CC).

If needed, we could revisit this and turn it into a whitelist or something, but for now,
the aim is to just blacklist “alive” projects where people read the alias.

Best,
Sam

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

      parent reply	other threads:[~2021-03-01 14:24 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07 14:28 [gentoo-dev] Non-maintainer commits and CI Agostino Sarubbo
2021-01-07 14:40 ` Sam James
2021-01-07 15:31 ` Joonas Niilola
2021-03-01 14:24 ` Sam James [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=6B266338-EBBC-46A0-A63F-DA1DD1AB582B@gentoo.org \
    --to=sam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    /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