Bugzilla: Reducing bugspam and finding patches

[Olav Vitters <olav bkor dhs org>]

There are a few changes in Bugzilla that I want to spam everyone about.
One is a patch report, the other changes are in the handling of
bug-buddy reports.

When you are drowning in bugspam wouldn't it be nice to get an easy
overview of your patches? Perhaps an overview of patches that need
reviewing in your product(s)? Maybe you'd like to see your submitted
patches that haven't been reviewed? Maybe even patches that still have
accepted-commit_now?

Despair no more. Elijah Newren's patch report coupled with my frontend
does everything you want and more. See for yourself and try the FREE
evaluation version at:
  http://bugzilla.gnome.org/reports/patch-status.cgi
That report has been linked from the 'Reports for Maintainers' section:
  http://bugzilla.gnome.org/reports/reports.cgi#maintainers
(Above comment was a subtle hint to ensure everyone bookmarks both links)


That was the patch report. Now on to the bug-buddy reports. There are
some tools to reduce the amount of bugspam you receive.
Basically you want to avoid bugspam that is:
1. Not for your product
2. An OpenOffice.org crasher
3. Already fixed (duplicate)

These can now be avoided if the bugreport is a crasher reported using
bug-buddy.

1. Not for your product
   This usually occurs with bug-buddy reports. You get a new crasher,
   but it is for another product. We can now move these bugreports
   automatically using the filename of the crashed program. When the
   bug is moved a warning will be added: "Bugreport moved from...". See
   for example: http://bugzilla.gnome.org/show_bug.cgi?id=307574
   (scroll below the stacktrace)

   If your product receives a lot of misreported bugs, and think they
   follow a pattern, contact Bugsquad (mailing list or #bugs). This can
   be the name of a program and the product it should be moved to, but
   other suggestions/ observations are welcome as well.

   Note: The bugreports will *not* be moved from every product. For a
   bugreport to be moved, the original product has to have at least one
   configured program. This was done on purpose as not to move
   (example) gtk+ bugreports back to gnome-panel.

2. OpenOffice.org crashers
   Bugzilla.gnome.org has been rejecting OpenOffice.org crashers since
   May 19. Since that time we've rejected over 300 of those.

3. Already fixed (duplicate)
   Some crashers have been fixed a long time ago, but they still receive
   daily bugreports. These bugreports can now be rejected automatically.
   For this the first 5 functions of the stacktrace are used, coupled
   with the GNOME version (to prevent regressions being rejected).

   If you have such a bug and it still receives a lot of duplicates,
   please contact Bugsquad with the bug number.


Persons interested in doing the work yourself or those afraid of
Bugsquad, please see:
http://cvs.gnome.org/viewcvs/*checkout*/halloween/bugzilla.gnome.org/program-map.txt
(The file to modify + documentation for #1 -- moving of bugreports)

and
http://cvs.gnome.org/viewcvs/*checkout*/halloween/bugzilla.gnome.org/crashers-map.txt
(The file to modify + documentation for #3 -- rejecting fixed crashers)

If above isn't clear, please contact me.

-- 
Regards,
Olav