1 |
On 3 October 2013 05:43, yac <yac@g.o> wrote: |
2 |
|
3 |
> I'd be cautious about involving users in this as it very often happens |
4 |
> to myself that something breaks, I get mad and then figure it was my |
5 |
> own fault (eg. messing with cflags I shouldn't mess with) |
6 |
> |
7 |
|
8 |
That does happen from time to time on the CPAN Testers network, the great |
9 |
thing about this is though, that there exists a test report, user err or |
10 |
not. |
11 |
|
12 |
And it is the job of the person who manually looks into bug reports to |
13 |
determine if they're a clear indication of a real bug being exhibited, or |
14 |
if its a user configuration problem. |
15 |
|
16 |
And if a CPAN Author wants, they can contact a sender and ask for more |
17 |
context if the CPAN author feels it relevant. |
18 |
|
19 |
This is basically an inversion of bug reporting mechanics in cases of |
20 |
trivial accidents user side that might otherwise simply not get reported, |
21 |
because it becomes the developers duty to follow up on a failed build if |
22 |
they think its relevant. |
23 |
|
24 |
Also, it helps with the bug reporting process, and helps users diagnose |
25 |
their own bugs, because they can, upon seeing a test/build failure, check |
26 |
the bug tracker *and* the report matrix, and see if other users are also |
27 |
exihibiting the failure, to help them get an idea of what is causing the |
28 |
failure, by comparing reported variables. |
29 |
|
30 |
Then, a user can say "Oh look, see, there's a boat load of tests failing on |
31 |
x86 with only this specific USE flag, there's no open bug for that, so I'll |
32 |
open one, and give the maintainer a lot of context on what looks to be the |
33 |
problem by linking directly to a handful of failed reports". |
34 |
|
35 |
This, would also be incidentally convenient for that old "ANSI Term Escape |
36 |
codes" problem, because the report/log submission would be automated ( |
37 |
giving us full control over how reports are performed ), and we could have |
38 |
a custom interface for displaying such reports that handled any submitted |
39 |
escape codes graciously, decoupling us from needing to find a way to handle |
40 |
that problem in bugzilla. |
41 |
|
42 |
Just the unfortunate part here is there are no off-the-shelf products for |
43 |
this problem space, so somebody would have to develop one. |
44 |
|
45 |
-- |
46 |
Kent |