Re: developer bug fixing statistics now available

Lukas Kahwe Smith wrote: > Greg Beaver wrote: > >> I understand why some think this is unfair, but I think the benefits >> outweigh the inconvenience. For instance, should there be a change of >> developer (something that will happen more often as PEAR ages), tracking >> down who actually fixed a problem that has resurfaced is much easier if >> the bug is assigned to the developer. > > Ok, in that case the quick fixes need to set the assigned users as > well. The way the stats are now I think its more harmful than helpful. > But if in the future the quick fixes ensure that the right person is > assigned, then the current "unfair" state will fix itself for most > developers eventually. Those who's pride is hurt should maybe get some > way to request a list produced by Martin's query, so that they can go > through the bug database manually. OK, here's what I can do for folks: 1) modify the bug code so that if a bug is marked "Closed" it auto-assigns (quick fixes not being necessary). This would be great, actually, I always have to type, click, click again, now it would be click click. :) 2) using the query I wrote for http://pear.php.net/~greg/helpdevs.php I will simply update all closed bugs without an "assign" and assign it to the person who closed the bug. I've taken a look at a large sampling, and all of these are fixed bugs 3) Perhaps we could change the text "Closed" to "Fixed"? This would be clearer. #3 is optional. #1 and #2 I will do. This will fix all the stats with no pain. Any objections? Greg