1 |
On Sun, 19 May 2013 15:40:27 +0200 |
2 |
Jeroen Roovers <jer@g.o> wrote: |
3 |
|
4 |
> Private messages and public comments through bugzilla are so far |
5 |
> ignored, it seems, so let's try a venue where it's sure to cause a |
6 |
> flamewar instead. My apologies for the inconvenience. |
7 |
|
8 |
Since you are the BW lead, I have followed your suggestion and done so |
9 |
since; but as I stated last time, there's no indication for others to |
10 |
follow this as far I can see. Maybe there is, then please show us. |
11 |
|
12 |
> On Sat, 18 May 2013 21:08:53 +0000 |
13 |
> bugzilla-daemon@g.o wrote: |
14 |
> |
15 |
> > DO NOT REPLY TO THIS EMAIL. Also, do not reply via email to the |
16 |
> > person whose email is mentioned below. To comment on this bug, |
17 |
> > please visit: https://bugs.gentoo.org/show_bug.cgi?id=470392 |
18 |
> > |
19 |
> > Bug ID: 470392 |
20 |
> > Summary: Please stabilize =dev-libs/libconfig-1.4.9-r1 |
21 |
> |
22 |
> We agreed a little while ago that bug Summaries should start with an |
23 |
> atom, if possible, and explain the action later. Also, robotically |
24 |
> filing thousands of bugs and making them say "please" every time isn't |
25 |
> going to endear anyone to your cause. So do something like this: |
26 |
> |
27 |
> "<cat/pkg-version> stabilisation request" |
28 |
> |
29 |
|
30 |
This is missing a reference URL or at least the ML thread subject; last |
31 |
time I asked, I didn't got either and wasn't able to find this in a |
32 |
reasonable amount of time. I find some irrelevant policy discussions |
33 |
but nothing that indicates the order in the summary. |
34 |
|
35 |
There are some developers that tend to point to history this way, they |
36 |
don't take into account how though it can be to search these threads if |
37 |
you don't use the wrong keywords to find the wrong subject. |
38 |
|
39 |
In 5 years from now, I don't think anyone is going to find "robo-stable |
40 |
bugs" searching for "please stabilize", "bug summary order" or any other |
41 |
thing along those lines. |
42 |
|
43 |
I could read the whole history, but that keeps me from contributing. |
44 |
|
45 |
> > URL: |
46 |
> > http://packages.gentoo.org/package/dev-libs/libconfig? arches=linux |
47 |
> |
48 |
> Is this URL useful to include, or did you just want to abuse every |
49 |
> last feature found in pybugz? Wouldn't maintainers already know where |
50 |
> to find this kind of information? Who do you think is your audience? |
51 |
|
52 |
+1 |
53 |
|
54 |
> > Severity: enhancement |
55 |
> |
56 |
> Is a stabilisation an enhancement per se? If all stabilisations are |
57 |
> enhancements, then why isn't Severity set to Normal instead? (What is |
58 |
> an enhanced severity to begin with, Mozilla?) |
59 |
> |
60 |
> > Priority: Normal |
61 |
> |
62 |
> This is where you probably wanted to set something similar to |
63 |
> Enhancement above, but again you probably shouldn't. Normal |
64 |
> stabilisation bugs are normal, not less than normal. |
65 |
|
66 |
Severity and Priority on the Gentoo Bugzilla have always been weird to |
67 |
me; I would love to hear from someone who is actually using either of |
68 |
those to sort their bugs and using them happily, because the |
69 |
inconsistency applied by different people is making a mess of them. |
70 |
|
71 |
The only case where I see them as useful is when people raise them to |
72 |
a higher priority for bugs that are really more important than the |
73 |
average bug, it makes them stand out in their list. |
74 |
|
75 |
We should standardize these in a way we don't have to memorize what |
76 |
they mean for every different type of bug, as that's the only way it is |
77 |
really going to make these fields make much more sense than something |
78 |
we tend to normalize and forget about. Why are bugs that block users |
79 |
from being able to use the package given a "normal" priority? |
80 |
|
81 |
> > Is it OK to stabilize =dev-libs/libconfig-1.4.9-r1 ? |
82 |
> > |
83 |
> > If so, please CC all arches which have stable keywords |
84 |
> > |
85 |
> > for older versions of this package and add STABLEREQ keyword |
86 |
> > |
87 |
> > to the bug. |
88 |
> |
89 |
> My e-mail editor is messing up the line endings here, but your |
90 |
> messages already include double newlines - on bugzilla web pages as |
91 |
> well as in the e-mail it sends, so this is your broken pybugz script |
92 |
> again, I reckon? |
93 |
|
94 |
That's so we can print the bug mail and write notes in between. =) |
95 |
|
96 |
> Also, your script does not set the STABLEREQ keyword. People are |
97 |
> having to hunt down your robo-stabilisation requests and add it |
98 |
> themselves. You should just do it yourself or turn your script off. |
99 |
|
100 |
Maintainer(s) and arch team member(s) blamed me for setting this. :( |
101 |
|
102 |
-- |
103 |
With kind regards, |
104 |
|
105 |
Tom Wijsman (TomWij) |
106 |
Gentoo Developer |
107 |
|
108 |
E-mail address : TomWij@g.o |
109 |
GPG Public Key : 6D34E57D |
110 |
GPG Fingerprint : C165 AF18 AB4C 400B C3D2 ABF0 95B2 1FCD 6D34 E57D |