Unpleasant mass updates
Mass updates to Bugzilla have a few unpleasant side effects:
- Unless they're done by DKL with direct access to the database, they generate a lot of e-mail which buries actual updates.
- They destroy the usability of queries for "bugs modified in the last 60/45/30 days". It's a useful trick I learned from Arjan. But now all kernel bugs are recently modified.
The idea, I guess, is that developer has to rescan relevant bugs and either work on them, push them into NEEDINFO, or close them. If hackers are dilligent about it, auto-closer is harmless [and also, unnecessary -- ed]. In reality though, it just does not work that way [and the very existence of auto-closer is the proof -- ed]. At certain point, I started making extra-Bugzilla lists of bugs which look realistic to work on (e.g. have an active submitter who cooperates, for one thing). The rest just rots. I don't even have cycles to push WONTFIX on them (or, actually, I have time to close, but I don't want to deal with the fallout, so I just pretend not to see them -- the task made easier by the mass-update and the resulting mail avalanche).
P.S. My list of bugs is, like, 10 to 50 times smaller than Chuck's and DaveJ's. I don't understand how they cope. It seems impossible to me, so there must be some trade secret good kernel monkeys know.