| 1 |
On Thu, 24 Dec 2009 07:37:26 -0500 |
| 2 |
Richard Freeman <rich0@g.o> wrote: |
| 3 |
|
| 4 |
> I think we should definitely have some way of designating which |
| 5 |
> should be the contact for bugs. I've had some bugs sit around for a |
| 6 |
> while without being noticed because they were assigned to the herd |
| 7 |
> the package is in, and not to me personally, and I don't generally |
| 8 |
> work with that herd, and the project associated with the herd doesn't |
| 9 |
> generally maintain the package. |
| 10 |
|
| 11 |
That means the bug wasn't properly assigned... I've set up some rules |
| 12 |
[1] that might help there. It comes down to this: |
| 13 |
|
| 14 |
1) If one or more <maintainer> tags are listed, assign to the first one |
| 15 |
mentioned. |
| 16 |
2) If no <maintainer> tag is listed, assign to the first <herd> |
| 17 |
mentioned. |
| 18 |
3) CC everyone else listed (<maintainer>s and <herd>s). |
| 19 |
|
| 20 |
The rationale is that if one or more <maintainer>s are listed as well as |
| 21 |
one or more <herd>s, a bug wrangler shouldn't need to go find out if |
| 22 |
that maintainer happens to be on the <herd>'s alias as well (otherwise, |
| 23 |
why would it mention those maintainers separately?). |
| 24 |
|
| 25 |
The order in which <maintainer> and <herd> tags are listed isn't |
| 26 |
special, because <maintainer> goes before <herd> for the reason set out |
| 27 |
above. The order of multiple <maintainer> tags (or multiple <herd> tags) |
| 28 |
does matter: the first one you find is the Assignee, the others are |
| 29 |
CC'd. |
| 30 |
|
| 31 |
|
| 32 |
Regards, |
| 33 |
jer |
| 34 |
|
| 35 |
|
| 36 |
[1] http://www.gentoo.org/proj/en/qa/bug-wranglers/index.xml#doc_chap4 |
Archives