Not really. We do a passable job. Stuff gets dropped, lost,
deferred and forgotten, applied when it conflicts with other work
- much of this stuff that software wouldnt actually improve on over a
person
> Although this seems annoying, it's just one facet of the
> primary difference between Linux and a commercially based
> kernel : if you want to know how something works and how
> it's being developed, then you MUST participate, in this
> and other mailing lists.
That wont help you - most discussion occurs in private because l/k
is too noisy and many key people dont read it.
> > 3. There is no central bug tracking database. At least people
> > should know the status of the bugs they have found with some
> > releases.
>
> There is no central product, so there can be no central bug track.
> (see below)
Rubbish. Ask the engineering world about fault tracking. You won't get
"different products no central flaw tracking" you'll get extensive cross
correlation, statistical tools and the like in any syste, where reliability
matters
Many kernel bug reports end up invisible to some of the developers.
Alan
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/