| 1 |
Robin H. Johnson wrote: |
| 2 |
> Notes: |
| 3 |
> ------ |
| 4 |
> 1. For handling <herd>no-herd</herd>, we should add an entry into herds.xml to |
| 5 |
> catch it (maintainer-needed <at> g.o). Every herd listed in an ebuild MUST be in |
| 6 |
> herds.xml. |
| 7 |
|
| 8 |
As rbu pointed out, this is slightly incorrect. Most of my ebuilds |
| 9 |
contain no-herd. ;) As do others. |
| 10 |
|
| 11 |
> 2. Herds that do not wish to be contacted for specific bugs should add an |
| 12 |
> maintainer element stating that (and use 'ignoreauto' on the element). |
| 13 |
> This case however should be very rare, as the package probably doesn't |
| 14 |
> belong in the herd if the herd doesn't care about it. |
| 15 |
> 3. If you want the default assignment to go to a maintainer, and NOT the herd, |
| 16 |
> move the <herd> element further down in the metadata.xml! |
| 17 |
|
| 18 |
AFAIK, "default" now it is assign to maintainer and cc herd and nearly |
| 19 |
always herd is higher up in the file. So, [nearly] all ebuilds will have |
| 20 |
to change metadata.xml |
| 21 |
|
| 22 |
OT, Do the changes to the bugzie interface block bugzilla 3 migration? |
Archives