1 |
Thilo Bangert wrote: |
2 |
> "Robin H. Johnson" <robbat2@g.o> said: |
3 |
|
4 |
>> See the thread about automatic assignment for more about this. |
5 |
>> More importantly, once the automatic stuff goes into play, the |
6 |
>> existence of the herd tag will only matter on metadata that does not |
7 |
>> have any other maintainer. |
8 |
> |
9 |
> sorry - to have missed this earlier. |
10 |
> from your proposal: |
11 |
>> Case 2 - Metadata contains a single maintainer |
12 |
>> ---------------------------------------------- |
13 |
>> The herd field is not used. |
14 |
> |
15 |
> so, you want to ignore the herd tag, as soon as there is a single |
16 |
> maintainer tag? why? |
17 |
> |
18 |
> we have <herd> on every single package in the tree (well ~1900 packages |
19 |
> with <herd>no-herd</herd>). my guess is that most of the roughly 4500 |
20 |
> packages that currently have a <herd> and a <maintainer> which is not a |
21 |
> <herd>, will need to adjust their metadata to reflect the situation where |
22 |
> the maintainer should get the bug asssigned and the herd gets CC'd... |
23 |
> |
24 |
> IMHO the herd should always get an email on bugs with packages belonging |
25 |
> to the herd... if this is not the case, what is the purpose of the herd? |
26 |
> |
27 |
> or asked differently: what can the herd in <maintainer> give you that the |
28 |
> <herd> can't? |
29 |
|
30 |
I agree here, we have many packages that are assigned to a herd, with a |
31 |
certain member of that herd listed as maintainer. For example I'll use |
32 |
freetype since I've been working on it today: |
33 |
|
34 |
dirtyepic@tycho /usr/portage/media-libs/freetype $ cat metadata.xml |
35 |
<?xml version="1.0" encoding="UTF-8"?> |
36 |
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> |
37 |
<pkgmetadata> |
38 |
<herd>fonts</herd> |
39 |
<maintainer> |
40 |
<email>foser@g.o</email> |
41 |
</maintainer> |
42 |
</pkgmetadata> |
43 |
|
44 |
In this case, a bug should be assigned to foser and fonts@g.o |
45 |
should be CCed. Freetype has frequent security bugs and foser is |
46 |
usually not present to deal with them. If the herd wasn't CC'd there'd |
47 |
be trouble. |
48 |
|
49 |
Another case is where we have a maintainer who isn't a member of the |
50 |
herd, like dejavu for example. |
51 |
|
52 |
dirtyepic@tycho /usr/portage/media-fonts/dejavu $ cat metadata.xml |
53 |
<?xml version="1.0" encoding="UTF-8"?> |
54 |
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd"> |
55 |
<pkgmetadata> |
56 |
<herd>fonts</herd> |
57 |
<maintainer> |
58 |
<email>pva@g.o</email> |
59 |
<name>Peter Volkov</name> |
60 |
</maintainer> |
61 |
<longdescription> |
62 |
The DejaVu fonts are a font family based on the Vera Fonts release 1.10. Its |
63 |
purpose is to provide a wider range of characters while maintaining the |
64 |
original |
65 |
look and feel through the process of collaborative development. Available |
66 |
families (Sans = sans serif, Mono = monospaced): DejaVu Sans, DejaVu |
67 |
Sans Mono, |
68 |
DejaVu Sans Condensed (experimental), DejaVu Serif, DejaVu Serif Condensed |
69 |
</longdescription> |
70 |
</pkgmetadata> |
71 |
|
72 |
We would want bugs filed against dejavu to be CC'd to the fonts herd, in |
73 |
case pva isn't present or it's something more generally font-related. |
74 |
|
75 |
No matter what, if the herd tag is not "no-herd", it should be CC'd on |
76 |
all bugs. |
77 |
|
78 |
|
79 |
-- |
80 |
dirtyepic salesman said this vacuum's guaranteed |
81 |
gentoo org it could suck an ancient virus from the sea |
82 |
9B81 6C9F E791 83BB 3AB3 5B2D E625 A073 8379 37E8 (0x837937E8) |
83 |
|
84 |
-- |
85 |
gentoo-dev@g.o mailing list |