From: Steve Long <slong@rathaus.eclipse.co.uk>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [v4] Planning for automatic assignment computation of bugs
Date: Wed, 07 Jan 2009 07:53:34 +0000 [thread overview]
Message-ID: <gk1nl7$qhf$1@ger.gmane.org> (raw)
In-Reply-To: 1231236674.5292.122.camel@localhost
Peter Volkov wrote:
> ? ???, 04/01/2009 ? 18:57 +0100, Robert Buchholz ?????:
>> Accepting the fact that different teams have different preferences, we
>> need to find a solution for them to set theirs individually. This could
>> either be the order of elements in metadata.xml (and would set the
>> preference on a per-package basis) or some attribute in herds.xml
>> (which would be a global setting per herd, and we'd need to find a
>> default).
>
> It looks like we really need some per-team configuration for default
> assignment.
I agree, given that it's not going to affect running systems (I hope); in
the longer term, it would be nice to be able to configure by pkg, cat or
herd.
> Probably it's good idea to add 'weight' (or 'nice')
> attribute for <herd> and <maintainer> elements both in herds.xml and
> metadata.xml. Bug assignment field will be selected from the elements
> with minimal weight (least nice ;)).
Shouldn't the 'nicest' entity take it? ;)
A simple assignToHerd="yes|no|<unset>" (or 0|1) might be easier to deal with
(otherwise you're going to have a maintenance headache with the variant
levels?) and would deal with all the use-cases afaict; a team does [eg
kde/gnome] or does not want bugs, unless the category/CP/CPV merits a
change in that policy. Obviously if none set, use the maintainer list as-is
without filtering.
Sure, it can be done by patching the tree over time, but it seems crude and
a further maintenance + bug-wrangling burden for no benefit, when the
coders are on-hand and engaged to tweak the new impl.
OFC, a rush to completion is understandable, given how long this has been in
the planning; I'd argue that's a reason to go the final ten metres.
next prev parent reply other threads:[~2009-01-07 8:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-19 6:01 [gentoo-dev] [v4] Planning for automatic assignment computation of bugs Robin H. Johnson
2008-10-19 13:29 ` Robert Buchholz
2008-10-19 19:13 ` Robin H. Johnson
2008-10-19 13:47 ` Jeremy Olexa
2008-10-19 19:16 ` Robin H. Johnson
2008-10-19 13:49 ` Ulrich Mueller
2008-10-19 19:43 ` Robin H. Johnson
2008-10-19 19:51 ` Robin H. Johnson
2008-10-19 19:32 ` Alec Warner
2008-10-19 19:47 ` Robin H. Johnson
2008-11-13 20:22 ` Thilo Bangert
2008-11-13 6:04 ` Donnie Berkholz
2009-01-04 16:52 ` Robert Buchholz
2009-01-04 17:02 ` Mike Auty
2009-01-04 17:06 ` Jeroen Roovers
2009-01-04 17:15 ` Mike Auty
2009-01-04 17:57 ` Robert Buchholz
2009-01-04 18:12 ` Mike Auty
2009-01-06 12:54 ` Robin H. Johnson
2009-01-06 14:19 ` Mike Auty
2009-01-06 10:11 ` Peter Volkov
2009-01-07 7:53 ` Steve Long [this message]
2009-01-07 6:01 ` Tiziano Müller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='gk1nl7$qhf$1@ger.gmane.org' \
--to=slong@rathaus.eclipse.co.uk \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox