> Right. Simply because these lists are assembled by someone
> - who knows how to pick that reports from the mailinglists
> - who knows how to sort them in a useful way
> - who knows how to add the relevant folks on CC
That all needs to be done by someone initially yes. But then tracking what happens
afterwards is something that can be distributed. A difficult bug can take a long
time to resolve and generate a lot of messages; you don't want to require
the initial sorter to handle all that too.
It's much more scalable to let the developers update the state themselves
then once they handle the bug.
From time to time, I'll send this list to right people.