Hi,
is there any metric defined to see how the bug solving pro- cess has improved over time?
The main reason I'm asking is today's two mails regarding bug #24000 ("Update rsvg so styling SVG images with CSS works properly on Commons"). Reported more than a year ago, the solution found early on was to update rsvg. I would have suspected that to do that you execute an "rpm -Uvh" equiva- lent on the server farm and close the bug. Yet for months nothing happened at all, and then some keywords were added, removed and replaced.
From an outside perspective, this looks like (much) more energy is spent on managing the bugs than actually squashing them. But that of course is not only an outside perspective, but the biased view of a user who is affected by the bug, sees a possible solution on his screen and experiences the helplessness of being at the mercy of someone else :-). So is there any "scorecard" with more detailed data than the weekly report, i. e. minimum/average/maximum time to closure of bugs/non-bugs, some nice visualizations, etc.?
TIA, Tim