public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Robin H. Johnson" <robbat2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [v5] Planning for automatic assignment computation of bugs
Date: Thu, 6 May 2010 04:27:49 +0000	[thread overview]
Message-ID: <robbat2-20100506T041852-777567908Z@orbis-terrarum.net> (raw)
In-Reply-To: <4BE2242F.2030209@gentoo.org>

On Thu, May 06, 2010 at 04:06:39AM +0200, Sebastian Pipping wrote:
> .. and that they need to be split smartly to keep each working in a
> shared codebase.  python modules and three entry point scripts on it
> could work.
+1 on that.

>      package_pattern =
> re.compile('\\b(?P<category>[a-z0-9_+-]+-[a-z0-9_+-]+)/(?P<package>[a-z0-9_+-]+(?:[a-z_+]+[0-9]+|[a-z0-9_+-]+[a-z+]+))')
- Fails to match category 'virtual'.
- That PV matching looks really fishy.
- I would probably just steal the pkgatom stuff from pkgcore/Portage, as
  that's already a fairly canonical regex.

>  - If you stick with the original pattern, this patch may still help:
> http://git.goodpoint.de/?p=eassign.git;a=commitdiff;h=7ad3cd607589aba7a1528dbd0744a942d18065eb
I think most of this might have already from from one the above.

> > How is it integrated into workflow?
> > ===================================
> > [..]
> > 5. Javascript then appends the server results into the "Additional
> >    Comments" box: a suggested assignee and suggested CC values, with logic
> >    as to why.
> assign.py does not explain reasoning, yet.
Ok, major todo on adding it, see below for why.

> > Assignment/CC computing:
> > ========================
> > Step 1 - Summary line processing
> > --------------------------------
> > [..]
> > 3. Process ALL atoms in the summary line, using any after the first for CC
> >    only. (new in v4)
> 
> I'm unsure about the handling of order:
> it wouldn't work well for "dependency foo/bar missing on foo2/bar2".
That's part of why the reasoning output was needed.
The full output for that should be something like:
=========
Combined:
---------
To: $ADDR1
CC: $ADDR2,$ADDR3
Ignoring: $ADDR4, $ADDR5

For foo/bar:
------------
To: ...
CC: ...
Ignoring: ...

For foo2/bar2:
--------------
To: ...
CC: ...
Ignoring: ...
=========
(optionally with some CLI options to say give only the combined
version).

> > Step 2 - Metadata.xml contains only a herd
> > ------------------------------------------
> > 1. Take the herd element, and look up the herd in herds.xml to convert
> >    to an email address. This email address must be a valid bugzilla
> >    account.
> This may need a replacement map.  Think media-video versus video,
> perl-bugs versus perl, etc.
I'm saying the replacement map IS from the herds.xml data. For herds
that have multiple emails (normal mail vs. bugzilla address), we really
need to find a way to document both of them in herds.xml.

-- 
Robin Hugh Johnson
Gentoo Linux: Developer, Trustee & Infrastructure Lead
E-Mail     : robbat2@gentoo.org
GnuPG FP   : 11AC BA4F 4778 E3F6 E4ED  F38E B27B 944E 3488 4E85



  reply	other threads:[~2010-05-06  4:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-05-03 21:49 [gentoo-dev] [v5] Planning for automatic assignment computation of bugs Robin H. Johnson
2010-05-06  2:06 ` Sebastian Pipping
2010-05-06  4:27   ` Robin H. Johnson [this message]
2010-05-07 17:06     ` Sebastian Pipping

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=robbat2-20100506T041852-777567908Z@orbis-terrarum.net \
    --to=robbat2@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