----- Original Message -----
From: "Tim Starling" tstarling@wikimedia.org Reverting hundreds of bug property changes was labour intensive. It points to the need for better tools to deal with malicious behaviour in Bugzilla. I looked into the possibility of writing an automated revert tool as a command-line perl script integrated with Bugzilla, but it looked like it would be fairly complicated:
Might there be some relatively easy way to hack rate limiting into the code?
In general, except for triage WONTFIX runs, I shouldn't think any given user would need to comment on or status-change a bug more than about every minute or two, possibly with an exponential backoff.
Cheers, -- jra