(removed [EMAIL PROTECTED], [EMAIL PROTECTED] from CC.. this is more of a Bugzilla development question than openoffice stuff)
On Tue, May 10, 2005 at 05:37:07PM +0200, Olav Vitters wrote: > On Tue, May 10, 2005 at 12:03:22AM -0400, Luis Villa wrote: [..] > > * if they aren't useful, should we figure out a way to pattern match > > them and resolve them automatically? It seems like this might be > > useful for other patterns as well, though my brain is hosed enough > > right ATM that I can't think of any offhand. > > Halloween currently has matches for product/component. I'd like to add > a detection of the crashed program to that and allow someone to > configure to either: > * Do nothing > * Move the bug into another product/component (with warning) > * Reject it it with a custom error message > (forwarding could be done in procmail; before Halloween) I was thinking about above for a while now. I can't decide where to put in; Halloween or bug-buddy-import (bugzilla-new). Both have to parse the text of the bugreport, so I can develop this in both. Note that the main idea is to forcefully send a bugreport to another product/component. This should happen for library products. As I don't want to make a list of that (and it could get out of date).. I thought of the following: If a product has at least one configured application name, allow bugreports from that product to be moved. Eg.. sample configuration (product/component => path): bug-buddy/general => /usr/bin/bug-buddy epiphany/general => /usr/bin/epiphany Now if an Epiphany crasher is filed to bug-buddy it is redirected to epiphany in the general component (with an error added by bug-buddy-import). If the epiphany crasher was filed against gtk+ the bugreport is left there (because gtk+ has no config thing). I haven't decided on allowing regexps for the application / full path / base name. This won't work for general though.. hrm... not sure if it really matters because Halloween rejects those anyway. Pro (+)/cons (-) of both: Halloween: + Already has a directory for configuration stuff. Cron ensures that directory is regularly checked out. Ensures this is all in one places, and I'm not sure if I want random commits to bugzilla-new. - I do not have access to halloween (on the server). Makes development irritating (main reason why I haven't done this already). - Have to find a way to get the error message to bug-buddy-import (I want all error messages to be in bug-buddy-import). Possibly by adding some fields to the XML. I think I'll add something like previous-product and previous-component, which I can use for the error message. - Can't access Bugzilla (actually don't want that) Bug-buddy-import: + Totally under my control + Easier to add error messages - Don't like to have configuration in bugzilla-new. Should be all in one place.. eg Halloween. I think I'll nag for access to halloween.. -- Regards, Olav _______________________________________________ Gnome-bugsquad mailing list [email protected] http://mail.gnome.org/mailman/listinfo/gnome-bugsquad
