RFC: Linux Bug Tracking & Feature Tracking DB

[Timothy Covell <timothy.covell@ashavan.org>]

I'm sure that this has been proposed and discussed
before, and I'm sure that some of the software houses
like RedHat must do this internally, but here goes again....


First the obvious problem:

Just today, I had a problem with a system lockup on 2.4.16
which was fixed in 2.4.17.  Although, I try to read the changelogs,
most of them are so terse as to be worthless to anyone but the
kernel hackers themselves.   And few people beside the hackers
have time to read through all the patches just in case the pertinant
fix might be there (and if said person could readily do this, he
could probably code his own fixes!)


Present solution:

Kernel hackers spend lots of time reading email and replying.
This requires that kernel hackers are user friendly, can easily
recognize bugs, and easily recall fixes, have lots of time on
their hands, etc.



Proposed Solution:

A kernel bug and feature tracking system.  This would similar
to what you all know (like Bugtraq).   Entries might look something like:

Example bug:

bug #13697
Synopsys: Hard kernel lockup on 2.4.16 with ieee1394 SBP-2.
Solution: Patch file: pdrv54678
            http://patches.linux.org./pub/linux/v2.4/patches/p/drv/54678.diff
Platform: x86
Section: drivers
Subsection: ieee1394
Contact: joe_hacker@linux-ieee1394.sourceforge.net.
Web URL: http://linux1394.sourceforge.net

Note: All patches in 'diff -urc' format.

Example Feature:

Search Results on Keyword: SBP-2 	Platform: x86

Topic: SBP-2
Platform: x86
Section: drivers
Subsection: ieee1394
Support on 2.2.x-2.2.y and 2.4.x-2.4.present
Maturity: 7 (of 10)
Relevant Bug Reports:   #13697, #14999
Contact: joe_hacker@linux-ieee1394.sourceforge.net.
Web URL: http://linux1394.sourceforge.net




The outstanding issues:

1. The maintainer of this DB would need to receive patches
along with patch.lsm and feature.lsm like files from the code 
maintainers.   That means  that Linus, Alan, Marcello, Dave 
Jones, et al.,  might have to be involved.

2. DB would be a high volume site (at least that's the idea!)

3. Would would pay for and maintain it?  (I know, since I'm
the one putting forth the idea, it's mine to run with.  However,
a. I ain't rich.  b. following from a., I have no bandwidth 24kbps
dialup.)




That's my RFC.


timothy.covell@ashavan.org.