Re: Dedicated kernel bug database

[John Bradford <john@grabjohn.com>]

> Ok, have you looked at other bug tracking programs?  Can you find 
> something you can build on?  Take a look at this list of issue tracking 
> software:
> http://www.a-a-p.org/tools_tracking.html
> It has a lot of possibilities... different combinations of features and 
> implementation languages.
> 
> Could you perhaps expound a bit on your statement "there is nothing 
> about [bugzilla] that I think [is] right at the moment"?

* It uses Javascript in the search forms
* The search forms are not intuitive to use
* It's difficult to check that you're not reporting a duplicate bug
* It's almost all only web-based
* There is no way that you can track different versions to the extent
  we need to.

The last point is the one that I think is most important.

Whenever somebody posts a bug report to LKML, quite often the first
thing somebody asks them is whether they have tried another kernel
version.  Most people don't have the time to try more than, say,
three different versions, and a lot of people might not want to use
the 2.5 development tree.

We _need_ a way to add data to a bug report like this:

* Original bug reporter reports a bug in 2.4.20.  It was also in
2.4.19

* Somebody else tries older versions, and discovers that it was
introduced in 2.4.15

* A third person discovers that recent 2.5 kernels are not affected,
because the code has been re-written.

Each time, information is added to the bug database _in a way that can
be easily searched_, not just as comments which cannot.

I don't know of an existing bug database system which can do that, or
is close to being able to do that.

John.