From: Peter Volkov <pva@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [v4] Planning for automatic assignment computation of bugs
Date: Tue, 06 Jan 2009 13:11:14 +0300 [thread overview]
Message-ID: <1231236674.5292.122.camel@localhost> (raw)
In-Reply-To: <200901041857.28125.rbu@gentoo.org>
В Вск, 04/01/2009 в 18:57 +0100, Robert Buchholz пишет:
> On Sunday 04 January 2009, Mike Auty wrote:
> > Jeroen Roovers wrote:
> > > The order ("first maintainer as assignee" or "first maintainer/herd
> > > as assignee") is open to discussion and I think this is the proper
> > > forum to have that discussion.
>
> I actually implemented it this way before (only that I had all herds
> with higher priority than all maintainers, which is the reverse of your
> patch).
>
> 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. 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 ;)). IMO best is to assign on first
(any) maintainer in this list and on first (any) herd if there is no
maintainer elements there. If weight is defined in multiple places, per
category weight overrides weight from herd.xml and weight in
metadata.xml overrides everything. This allows easy way to define any
policy team wants but still allow maintainer to override team
preference. What do you think?
--
Peter.
next prev parent reply other threads:[~2009-01-06 10:11 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 [this message]
2009-01-07 7:53 ` [gentoo-dev] " Steve Long
2009-01-07 6:01 ` [gentoo-dev] " 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=1231236674.5292.122.camel@localhost \
--to=pva@gentoo.org \
--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