Re: New (now current development process)

Andrew Morton
2005-10-31T06:08:49Z

Andi Kleen <ak@suse.de> wrote:
>
> On Monday 31 October 2005 02:22, Andrew Morton wrote:
>
> > There is nothing stopping anyone from working with the originators to get
> > these things fixed up at any time.
> >
> > Why is it necessary for me to chase maintainers to get their bugs fixed?
> >
> > Why are maintainers working on new features when they have unresolved bugs?
>
> Because zero bugs is just unrealistic and they would never get anything done
> if that was the requirement?
>
> (especially considering that a lot of the bugs at least on x86-64 are
> hardware/firmware bugs of some sort, so often it is not really a linux
> bug but just a missing ha^w^wwork^w^w^w^wfix for something else)
>
> I agree regressions are a problem and need to be addressed, but handling all
> non regressions on a non trivial platforms is just impossible IMHO...
>
> Perhaps it would be nice to have better bug classification: e.g.
> regression/new hardware/reported by more than one person etc. I think
> with some prioritization like that it would be much easier to keep the bugs
> under control.

Well sure. But who does that? It should be the relevant maintainer, IMO.
If that's the way in which he chooses to work. Expecting some third party
to do this on a kenrel-wide basis won't fly.

> ...
> Sometimes bugs are less important than others.

I don't believe that what we're seeing is some prioritisation process. The
problem is that some bugs are *harder* than others, and people are just
ducking things which cannot be locally reproduced.