From: Ian Stakenvicius <axs@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages
Date: Sun, 6 Dec 2015 12:26:59 -0500 [thread overview]
Message-ID: <AFB9D0C6-5237-47A9-BBC8-0E792D3FE2FC@gentoo.org> (raw)
In-Reply-To: <CAGfcS_nMqyq_o3kw=nc-fD=shASE0Labe5rNAhivazgu1xAT9w@mail.gmail.com>
> On Dec 6, 2015, at 11:52 AM, Rich Freeman <rich0@gentoo.org> wrote:
>
>> On Sun, Dec 6, 2015 at 11:09 AM, Michael Orlitzky <mjo@gentoo.org> wrote:
>> On 12/06/2015 11:00 AM, Michał Górny wrote:
>>>>
>>>> Of course. Add the commit author, too: I want to know if I break someone
>>>> else's package.
>>>
>>> So far, can't do that since we don't know which commit exactly broke. I
>>> don't want to do any heuristics that could blame the wrong person.
>>
>> Is the testing performed per-push rather than per-commit? Either way, I
>> would like to get a notification that something broke, even if it wasn't
>> my commit at fault. Just change the word "blame" to "alert" so no one
>> feels slandered.
>
> ++
>
> This isn't about shaming people. It is about alerting that the tree
> is broken. I think we can agree that when packages don't build it is
> a problem, and it won't fix itself.
>
> How many commits typically go by in-between checks? Would it be
> practical to just alert any commit author in that time range? Sure,
> it would generate a bit of spam, but:
>
> 1. Better to get problems fixed sooner than later.
> 2. The overall improved attention to QA will hopefully reduce the
> error rate and thus make the number of emails regulate themselves.
>
> One of the first steps towards reducing errors is to increase their visibility.
>
Couldn't we just alert the people listed in the metadata for the packages affected? Even if it wasn't them that caused the breakage, aren't they ultimately responsible for making sure the package works? They could ping the actual committer...
next prev parent reply other threads:[~2015-12-06 17:36 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-06 14:36 [gentoo-dev] RFC: automatically mailing people on pkgcheck problems with their packages Michał Górny
2015-12-06 14:54 ` Dirkjan Ochtman
2015-12-06 15:31 ` Michael Orlitzky
2015-12-06 16:00 ` Michał Górny
2015-12-06 16:09 ` Michael Orlitzky
2015-12-06 16:49 ` Michał Górny
2015-12-06 17:25 ` Michael Orlitzky
2015-12-06 17:49 ` Andreas K. Huettel
2015-12-08 7:01 ` Michał Górny
2015-12-06 16:52 ` Rich Freeman
2015-12-06 17:26 ` Ian Stakenvicius [this message]
2015-12-06 18:58 ` Rich Freeman
2015-12-08 0:05 ` Alec Warner
2015-12-08 0:27 ` Rich Freeman
2015-12-08 2:19 ` Anthony G. Basile
2015-12-08 3:21 ` Rich Freeman
2015-12-08 6:59 ` Michał Górny
2015-12-08 19:11 ` Daniel Campbell
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=AFB9D0C6-5237-47A9-BBC8-0E792D3FE2FC@gentoo.org \
--to=axs@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