Re: RFC: Linux Bug Tracking & Feature Tracking DB

David Ford
2002-01-02T02:49:30Z

>
>
>It is not for anybody who handles large amounts of mail. I have yet to see
>a browser which does even a half-assed attempt at doing email right.
>

I handle thousands of emails a day, over a hundred emails distinctly to
me, not a list. I like mozilla most, but don't think I like the
footprint or everything about it ;)

>Here (emacs + mh-e): ^ on the message, RET to confirm the folder. Managing?
>No sweat, it is just another mail folder, to be handled by the same
>commands my fingers do on their own now.
>

As I mentioned to DJ, this is fine for you, your personal database, but
it serves no purpose for anyone else and doesn't scale well for large
amounts of reference material.

>Plus the problem that thousands of (well meaning, but completely useless)
>reports clog up bug<foo>, rquiring hand-cleaning by somebody who _really_
>knows about the system. I.e., exactly the person whose work you want to
>spare.
>

Untidied bug reports can be flushed out of the system, they can be
<insert action>. By making a more intuitive system, these bug reports
could be fleshed out better or coallated when appropriate. By having an
open system, anyone can do the maintenance. You can choose different
pools for the entries and keep the chaff "outside" until it is weeded
through or discarded.

>Look at the FAQ for the kernel (helpfully compiled by this list). Problems
>that get identified tend to get fixed fast, so working at documenting them
>in detail makes no sense at al.
>
>If you want to know what is broken in _development_ kernels, you have to
>read this list.
>

Not everything needs to be documented or documented in detail.
Sometimes a simple "loopback compile err, 'loopback.c:417:foo is not
defined' is fixed in 2.2.2." is quite sufficient. People with 2.2.1
will recognize the need to upgrade or generate a patch to solve their
problem. The FAQ doesn't address everything and not everything is
broken. A 'bug' database is sometimes a misnomer.

Neither the DB nor the list replace each other. They augment each other.

David