Dedicated kernel bug database
What are your ideas???
Regards, Dean.
On Fri, 20 Dec 2002 09:48:53 +0000 (GMT) John Bradford <[email protected]> wrote:
[CC list trimmed]
Quoted 3 lines
Quoted 1 line
I've got loads of ideas about how we could build a better bug database
Go ahead, knock yourself out. Come back when you're done.
Not sure what you mean. I do intend to start coding a new bug database system today, and I'll announce it on the list when it's ready. If nobody likes it, I wasted my time.
Quoted 8 lines
Quoted 6 lines
- for example, we have categories at the moment in Bugzilla. Why? We already have a
MAINTAINERSfile, so say somebody looks up the relevant maintainer in that list, finds them, then goes to enter a bug in Bugzilla. Now they have to assign it to a category, and different people may well assign the same bug to different categories - immediately making duplicate detection more difficult.Have you actually looked at the maintainers file?
Yes.
Quoted 1 line
It's a twisted mess of outdated information,
Then it should be updated, that is nothing to do with Bugzilla.
Quoted 1 line
in no well formated order.
Looks easy enough to parse with regular expressions to me.
Quoted 2 lines
The category list in Bugzilla was an attempt to bring some sanity to the structure,
By adding an extra layer of abstraction. I don't agree that that helps.
Quoted 2 lines
though I won't claim it's perfect. We really need a 3-level tree, but that's a fair amount of work to code.
I disagree, (that we need a 3-level tree).
John.
-
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/
Quoted 10 lines
Quoted 8 lines
Quoted 4 lines
Quoted 2 lines
I've got loads of ideas about how we could build a better bug database
Go ahead, knock yourself out. Come back when you're done.
Not sure what you mean. I do intend to start coding a new bug database system today, and I'll announce it on the list when it's ready. If nobody likes it, I wasted my time.
What are your ideas???
* Automatic parsing of things like .config files and oopsen.
* Version tracking that is more suited to a codebase that has at least 5 very active trees.
* Fully controlable by E-Mail, not only web.
Those are the ones I'm most interested in initially. Other things can follow.
I'd had a lot of comments saying that it would be better to either add these ideas to Bugzilla, or to write a generic bug database, and not make it specific to kernel development.
The reasons I'm _not_ doing either of those is mostly:
* I don't like Bugzilla at all
* It's easy to make a kernel-specific bug database generic, and not so easy to make a generic database kernel-specific
Incidently, can your TV set top box browse the web, or just send E-Mail? It would be quite cool if you could go through the bug database using it :-)
John.