bugzilla bugzappers?

Michael Schwendt mschwendt at gmail.com
Sat Nov 6 09:29:35 UTC 2010


On Sat, 06 Nov 2010 04:17:59 +0000, Jóhann wrote:

> On 11/06/2010 02:11 AM, Ralf Corsepius wrote:
> > On 11/05/2010 10:06 PM, Michael Schwendt wrote:
> >> On Thu, 04 Nov 2010 23:58:21 +0000, Jóhann wrote:
> >>
> >>> On behalf of all reporters that have never received a response from a
> >>> maintainer on a component they have reported against I not only ask the
> >>> ABRT maintainers to block any reports against those component that a
> >>> maintainer has not responded but I also request that those components
> >>> get removed from bugzilla.redhat.com.
> >> Weird idea. Not sure it's worth commenting on it. The problem with
> >> maintainers not responding to some tickets can have multiple reasons.
> >> Some components literally are flooded with new tickets. Hundreds.
> >> Thousands.
> > These packages should be examined and analysed individually and
> > consequences be drawn upon, if neccessary even if they might be unpleasant
> 
> Agreed...
> 
> JBG
 
Agreeing doesn't fix the resource problems. For special packages, it's
obvious.

  http://bugz.fedoraproject.org/kernel
  1374 bugs found

For others, it isn't.

  http://bugz.fedoraproject.org/gftp
  49 bugs found

But the bugzapping EOL script treats all packages equally, afaik. It would
also kill off _the single one_ major crasher ticket for a maintainer's single
package just because nobody replies in bugzilla.


More information about the devel mailing list