1 |
On Sun, Dec 6, 2015 at 11:09 AM, Michael Orlitzky <mjo@g.o> wrote: |
2 |
> On 12/06/2015 11:00 AM, Michał Górny wrote: |
3 |
>>> |
4 |
>>> Of course. Add the commit author, too: I want to know if I break someone |
5 |
>>> else's package. |
6 |
>> |
7 |
>> So far, can't do that since we don't know which commit exactly broke. I |
8 |
>> don't want to do any heuristics that could blame the wrong person. |
9 |
>> |
10 |
> |
11 |
> Is the testing performed per-push rather than per-commit? Either way, I |
12 |
> would like to get a notification that something broke, even if it wasn't |
13 |
> my commit at fault. Just change the word "blame" to "alert" so no one |
14 |
> feels slandered. |
15 |
> |
16 |
|
17 |
++ |
18 |
|
19 |
This isn't about shaming people. It is about alerting that the tree |
20 |
is broken. I think we can agree that when packages don't build it is |
21 |
a problem, and it won't fix itself. |
22 |
|
23 |
How many commits typically go by in-between checks? Would it be |
24 |
practical to just alert any commit author in that time range? Sure, |
25 |
it would generate a bit of spam, but: |
26 |
|
27 |
1. Better to get problems fixed sooner than later. |
28 |
2. The overall improved attention to QA will hopefully reduce the |
29 |
error rate and thus make the number of emails regulate themselves. |
30 |
|
31 |
One of the first steps towards reducing errors is to increase their visibility. |
32 |
|
33 |
-- |
34 |
Rich |