| 1 |
Daniel Drake posted <42D649CE.3070101@g.o>, excerpted below, on |
| 2 |
Thu, 14 Jul 2005 12:17:34 +0100: |
| 3 |
|
| 4 |
> Chris White wrote: |
| 5 |
>>>never reassign a bug |
| 6 |
>> |
| 7 |
>> |
| 8 |
>> Ok, I have a section on how to re-assign the bug to the maintainer if |
| 9 |
>> you're the reporter, so you don't want that at all is what you're |
| 10 |
>> saying? Just let bug-wranglers handle it? |
| 11 |
> |
| 12 |
> Yes, I'm pretty much saying that. Thinking back to the situation that |
| 13 |
> prompted me to note this down, a kernel bug came in. bug-wranglers |
| 14 |
> assigned it to kernel. The reporter then reassigned it to me(!?) without |
| 15 |
> me even responding, with a comment like, "dsd this one is for you". Since |
| 16 |
> when do our users get to choose which developer fixes their bug? I found |
| 17 |
> this quite rude and replied with a (probably too harsh) comment and |
| 18 |
> reassigned it back to kernel. The user then sent me an apologetic email, |
| 19 |
> stating that he didn't know much about Gentoo development and asked me to |
| 20 |
> explain the reassignment procedures. |
| 21 |
> |
| 22 |
> My response to that: Just leave reassignment to the developers (wranglers |
| 23 |
> included). |
| 24 |
|
| 25 |
Counter-example. The amd64 team specifically mentions in their |
| 26 |
documentation on keywording that keyword bugs can be specifically assigned |
| 27 |
to amd64. Likewise with the multilib-strict bugs, they were to be |
| 28 |
assigned to amd64. Of course, that's an arch team, not an individual |
| 29 |
developer, but the point stands, if these bugs are being filed on specific |
| 30 |
request of some team or individual developer (as with testing of some |
| 31 |
package or another), there's no reason to bother bug-wranglers with it, |
| 32 |
when all they are going to do is assign it to the same folks that |
| 33 |
requested it, that got the user testing and filing the bug in the first |
| 34 |
place! |
| 35 |
|
| 36 |
So... something like the following (first draft off the top of my head, |
| 37 |
can probably be rewritten rather better than this): |
| 38 |
|
| 39 |
"Leave the bug assignment alone, unless you are sure you know who to |
| 40 |
assign it to. For most bugs and reporters, that means let the |
| 41 |
bug-wranglers handle it, unless the bug has been filed in response to a |
| 42 |
specific request by the package maintainer/herd or your arch team. If you |
| 43 |
are reading this, it probably means leave it alone." |
| 44 |
|
| 45 |
-- |
| 46 |
Duncan - List replies preferred. No HTML msgs. |
| 47 |
"Every nonfree program has a lord, a master -- |
| 48 |
and if you use the program, he is your master." Richard Stallman in |
| 49 |
http://www.linuxdevcenter.com/pub/a/linux/2004/12/22/rms_interview.html |
| 50 |
|
| 51 |
|
| 52 |
-- |
| 53 |
gentoo-dev@g.o mailing list |
Archives