Re: Linux 2.6.21

On Sunday, 29 April 2007 19:37, Andi Kleen wrote:
My personal experience with bugzilla is that it's very unfriendly to
reporters. IMHO it's suitable for tracking unresolved problems along with
debug patches, system information etc., but not for _reporting_ new ones.

What did you find unfriendly?

- You are required to select a category and 'component' for your report, which
often is difficult (especially if you're not a kernel expert)
- You need to have a bugzilla account (or to create one, if you don't)
- If you want to add an address to the CC list, it must be known to bugzilla
and there's no (obvious) way to check which addresses are known (bugzilla
rejects the report if there's a 'wrong' email address in the list) [IMO this is
really really broken.]
- You are asked to provide many details that need not be relevant and casual
reporters don't know that they can skip this part
- Attaching files is tedious and referring to attachments unintuitive

While I also cannot say I love it I don't find it any less unfriendly
than an email.

That depends (please see below).

Besides the primary point of bug tracking is not to be friendly
to someone, but to (a) fix the bugs and (b) know how many bugs
there for a given release. Any replacement would need to solve
this problem too.

For _tracking_ bugs, the bugzilla is more-or-less suitable.
For _reporting_ bugs, IMHO, it's not.

And I think they are two _totally_ conceptually different things. You report
a bug to let somebody know that there's a problem and this doesn't necessarily
mean that the problem has to be tracked. It may be very simple and immediately
resolvable, in which case registering it in bugzilla is a loss of time and
resources. If the problem _turns_ _out_ to be difficult, _then_ it'll need to
be tracked, but usually it's not known whether or not this is the case until
someone 'in the know' looks at the initial report.

For this reason there should be a simple means of filing initial bug reports
with someone to look at them and forward them to appropriate people who will
decide if the problem needs to be tracked. If they do, it's time to use
bugzilla. Not earlier.

Email does not solve it as far as I can see.

You are right, email is not suitable for tracking bugs. Still, it works quite
well as a means of sending initial reports.

Greetings,
Rafael
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/

Relevant Pages

  • Re: MODULE_MAINTAINER
    ... ever gone to bugzilla without killing well over ... used for a report) to search for similar reports and join them. ... bugs and then simply mark them as such once identified. ... As subsystem maintainer, I am actively using kernel.org's bugzilla and I ...
    (Linux-Kernel)
  • Re: FC6 through the rear view mirror
    ... package maintainers use bugzilla as a guide for things that need to be ... maintainers to the bug reporters because they haven't fixed the bugs ... report them here even though few of the package maintainers monitor this ...
    (Fedora)
  • Re: FC6 through the rear view mirror
    ... maintainers to the bug reporters because they haven't fixed the bugs ... that you reported (though a search for your e-mail address in bugzilla ... report them here even though few of the package maintainers monitor ...
    (Fedora)
  • Re: Linux 2.6.21
    ... and it's an _advantage_ of the kernel Bugzilla to see more ... than 1600 open bugs because this tells how bad we are at handling bugs. ... Don't say that "bugzilla tells how bad we are at handling bugs". ... there's nothing more frustrating then spending a good chunk of time trying to find a similar bug, then jumping through all the bugzilla hoops to file a report to eventually get a message 'closed becouse it's a duplicate report), then have to go and track down what it's a duplicate of, read through that bug report, only to find that it's not solved there either, and to top it off, the people working on that bug won't see my report or that I'm available to troubleshoot it. ...
    (Linux-Kernel)
  • Bugzilla and management thereof
    ... reporting it to bugzilla. ... the report could be updated to note that it still applies to f7. ... auto-closes bugs from older releases*. ... I was assuming that if Ray decided it was an upstream bug he'd ...
    (Fedora)