It would be good. Right now I know for a fact that a lot of people read
LKML with various filters in place (or just very spottily), so I have a
feeling that while people try to track regressions, many people are
probably less aware of these things than they should be. And sometimes the
"handled-by" ends up being inaccurate (maybe somebody replied to the
original problem, but it became obvious that it was somewhere else, and
they remain "handled-by" even though the person doesn't actually handle
it).
It would probably also make sense to add some of the bigger subsystem
maintainers to the Cc (and/or with a mailing list for regressions?)
I think the regression list is _extremely_ valuable, but the problem I
see is that it's not necessarily reaching all the involved people.
The other problem is that I think the old reports (especially the ones
that haven't had reporter feedback in the last two weeks) end up being not
just stale, but they sort at the top, so when the right people _do_ look
at the list, the natural way to do so with email is to look at the first
ones first, and they *all* tend to be stale.
So the reaction is often "need more info" or "I think this was fixed
already two weeks ago, but there hasn't been any reply". Which is
psychologically really bad, because after you've seen three or four of
those, you just dismiss the rest (even if the later ones then may be much
more relevant!)
This is why I have always been advocating so aggressive culling of
regressions and bug-reports - stale bug-reports are worse than useless,
they actually _hurt_.
Linus
--
