Thilo Bangert wrote:
> "Robin H. Johnson" <[EMAIL PROTECTED]> said:

>> See the thread about automatic assignment for more about this.
>> More importantly, once the automatic stuff goes into play, the
>> existence of the herd tag will only matter on metadata that does not
>> have any other maintainer.
> 
> sorry - to have missed this earlier.
> from your proposal:
>> Case 2 - Metadata contains a single maintainer
>> ----------------------------------------------
>> The herd field is not used.
> 
> so, you want to ignore the herd tag, as soon as there is a single 
> maintainer tag? why?
> 
> we have <herd> on every single package in the tree (well ~1900 packages 
> with <herd>no-herd</herd>). my guess is that most of the roughly 4500 
> packages that currently have a <herd> and a <maintainer> which is not a 
> <herd>, will need to adjust their metadata to reflect the situation where 
> the maintainer should get the bug asssigned and the herd gets CC'd...
> 
> IMHO the herd should always get an email on bugs with packages belonging 
> to the herd... if this is not the case, what is the purpose of the herd?
> 
> or asked differently: what can the herd in <maintainer> give you that the 
> <herd> can't?

I agree here, we have many packages that are assigned to a herd, with a
certain member of that herd listed as maintainer.  For example I'll use
freetype since I've been working on it today:

[EMAIL PROTECTED] /usr/portage/media-libs/freetype $ cat metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd";>
<pkgmetadata>
<herd>fonts</herd>
<maintainer>
  <email>[EMAIL PROTECTED]</email>
</maintainer>
</pkgmetadata>

In this case, a bug should be assigned to foser and [EMAIL PROTECTED]
should be CCed.  Freetype has frequent security bugs and foser is
usually not present to deal with them.  If the herd wasn't CC'd there'd
be trouble.

Another case is where we have a maintainer who isn't a member of the
herd, like dejavu for example.

[EMAIL PROTECTED] /usr/portage/media-fonts/dejavu $ cat metadata.xml
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd";>
<pkgmetadata>
<herd>fonts</herd>
<maintainer>
 <email>[EMAIL PROTECTED]</email>
 <name>Peter Volkov</name>
</maintainer>
<longdescription>
The DejaVu fonts are a font family based on the Vera Fonts release 1.10. Its
purpose is to provide a wider range of characters while maintaining the
original
look and feel through the process of collaborative development. Available
families (Sans = sans serif, Mono = monospaced): DejaVu Sans, DejaVu
Sans Mono,
DejaVu Sans Condensed (experimental), DejaVu Serif, DejaVu Serif Condensed
</longdescription>
</pkgmetadata>

We would want bugs filed against dejavu to be CC'd to the fonts herd, in
case pva isn't present or it's something more generally font-related.

No matter what, if the herd tag is not "no-herd", it should be CC'd on
all bugs.


-- 
dirtyepic                 salesman said this vacuum's guaranteed
 gentoo org          it could suck an ancient virus from the sea
  9B81 6C9F E791 83BB 3AB3  5B2D E625 A073 8379 37E8 (0x837937E8)

-- 
[EMAIL PROTECTED] mailing list

Reply via email to