| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Ulrich Mueller wrote: |
| 5 |
|>>>>> On Thu, 24 Apr 2008, Luis Francisco Araujo wrote: |
| 6 |
| |
| 7 |
|> | One other thing is that it is sometimes difficult to figure out to |
| 8 |
|> | whom a bug should be assigned, because metadata.xml for many packages |
| 9 |
|> | simply isn't clear. If you list a few developers as well as a herd, |
| 10 |
|> | does that mean you want bugs assigned to the herd or to a single |
| 11 |
|> | developer who happens to be in that list? Some packages list several |
| 12 |
|> | herds in metadata.xml. Bugs can be assigned to just one address |
| 13 |
| |
| 14 |
|> I'd say that in the case of a herd listed , the bug should be sent |
| 15 |
|> there. |
| 16 |
| |
| 17 |
| A common case is a herd plus a specific maintainer, and I think then |
| 18 |
| it should be assigned to the maintainer, with a CC to the herd's team. |
| 19 |
| |
| 20 |
|> If it doesn't specify a herd but several developers, sending the bug |
| 21 |
|> to any or all of them should be the rule. |
| 22 |
| |
| 23 |
| In this case, it should be assigned to the first developer listed, and |
| 24 |
| all others in CC. |
| 25 |
| |
| 26 |
|
| 27 |
If this is the case, I think this should be stated somewhere in the docs |
| 28 |
, since the order of listed maintainers don't have any priority, and I |
| 29 |
personally would prefer to keep it so. |
| 30 |
|
| 31 |
|
| 32 |
- -- |
| 33 |
|
| 34 |
Luis F. Araujo "araujo at gentoo.org" |
| 35 |
Gentoo Linux |
| 36 |
|
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v2.0.9 (GNU/Linux) |
| 39 |
|
| 40 |
iEYEARECAAYFAkgRUVIACgkQNir3WYj9aLoEjQCeIvFaInENgCOhz65K9CaywFa4 |
| 41 |
C7gAnjjQAT82gerNwWmModYBVEpVHBrF |
| 42 |
=V6VD |
| 43 |
-----END PGP SIGNATURE----- |
| 44 |
-- |
| 45 |
gentoo-dev@l.g.o mailing list |
Archives