public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sebastian Pipping <sping@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [v5] Planning for automatic assignment computation of bugs
Date: Thu, 06 May 2010 04:06:39 +0200	[thread overview]
Message-ID: <4BE2242F.2030209@gentoo.org> (raw)
In-Reply-To: <20100503214957.GA30113@orbis-terrarum.net>

On 05/03/10 23:49, Robin H. Johnson wrote:
> Known prototypes:
> =================
> http://dev.gentoo.org/~rbu/assign.py
> - I believe this prototype is fully up to date, it just takes
>   herds/metadata.xml as well as a string, and gives you the output the
>   commandline.
>   rbu: can you confirm that your prototype matches the proposal?

I have fork of that laying around here:
http://git.goodpoint.de/?p=eassign.git;a=summary

When rbu and I last talked about it we came to the conclusion that the
tool serves several distinct use cases ..

  - backend use by bugzilla
  - command line use on package X, even without a bug
  - security team usage (forgot the details)

.. 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.

I know that neither rbu nor me have resources for the code of this atm,
maybe idl0r has?  I'd like to be notified on progress, though.

Two regex related things I'd like to append:

 - I've been using this alternative regex for but title extraction
   elsewhere before, seems to work well:

     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+]+))')

 - If you stick with the original pattern, this patch may still help:

http://git.goodpoint.de/?p=eassign.git;a=commitdiff;h=7ad3cd607589aba7a1528dbd0744a942d18065eb


> 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.


> 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".


> 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.


Best,



Sebastian



  reply	other threads:[~2010-05-06  2:07 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 [this message]
2010-05-06  4:27   ` Robin H. Johnson
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=4BE2242F.2030209@gentoo.org \
    --to=sping@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