On Sun, 29 Apr 2007, Adrian Bunk wrote:
> >
> > Kernel bugzilla has 1600 open bugs BECAUSE IT SUCKS.
>
> OK, how do you suggest to track bugs in a way that doesn't suck?
I've tried to explain.
Bugzilla can be one _part_ of it, but anybody who thinks it's the "main
part" is really not being realistic. It's too cumbersome, and it's too
stupid.
Quite frankly, "lkml + google" is probably in many ways a *better* way to
search for problems. But yes, some manual smarts (and the _occasional_
pointer to bugzilla) is probably currently the only option.
Exactly because I don't think anybody has shown any better automation than
bugzilla. But that doesn't make bugzilla "the One Choice". That's not how
it works. If there is no automation, manual tracking is still better than
*crap* automation.
> Bug reports to linux-kernel have the big problem that they are lost if
> no developer immediately picks them up.
..and this is different from bugzilla exactly _how_?
Those things are lost too. As you yourself have pointed out. The fact that
you can search for them is _exactly_ as relevant as the fact that you can
search for lkml on google.
> What I do know is that the majority of them has never been proper
> debugged by a kernel developer knowing the subsystem in question.
And you blame the developers, but not bugzilla? Why are you so unable to
see bugzilla as part of the *cause* of the problem? You're perfectly happy
to blame other things, but bugzilla is somehow above blame?
Linus
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
