On Mon, Apr 14, 2008 at 01:04:12AM -0700, Andrew Morton wrote:

...
(And I don't think developers and maintainers _should_ spend time mucking
in bug-tracking systems.  They should have helpers who do all the
triaging/tracking/routing/closing work for them, and then provide other
developers with the results, letting them know what they should be spending
time on.  But there's a manpower problem).
...

Speaking as the one who was for a few years going again and again 
through all open bugs in the kernel Bugzilla:

The manpower problem isn't in handling the bugs in Bugzilla.

I'd claim that even if all bugs in the kernel would be reported in the 
kernel Bugzilla I alone would be able to do all the handling of incoming 
bugs, bug forwarding and doing all the cleanup stuff like asking 
submitters whether a bug is still present in the latest kernel.

The manpower problem is at the developers and maintainers who could 
actually debug the problems.

One problem are unmaintained areas.
Do we have anyone who would debug e.g. APM bugs?
And if I want to be really nasty, I'll ask whether we have anyone who 
understands our floppy driver...  ;)

And who would debug problems with old and unmaintained drivers, e.g. 
some old net or SCSI driver?

Note that I do not blame James or Jeff or whoever else for the latter - 
they might simply not have the time to spend a day or two for debugging 
some obscure problem on some obscure hardware.

And it could happen everywhere that maintainers simply don't have 
the time to cope with all incoming bug reports.

We have many people who write new bugs^Wcode.
But too few people who review code.
And too few people willing to maintain the existing code.

cu
Adrian

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed