This sounds like a good idea. Some of these bugs have been fixed but not
closed. Here's how I have been operating: if I fix a bug opened by
someone else, I let the bug reporter determine whether the report can be
closed. It might be good for people to review the bug reports they have
opened to see if some of them can be closed now.
Regards,
-Rick
Daniel John Debrunner wrote:
Since the start of this year I've been tracking the number of open
code bugs from the Jira filter 'Derby open code bugs'. (Helped by the
pie chart reporting now available on Jira).
For the first two months the number was somewhat flat around 210 but
in March has started to climb to around 240.
Here's a bar chart
http://people.apache.org/~djd/derby/DerbyOpenCodeBugs_16629_image001.gif
Interesting idea would be to set a target for the next release (May?),
something like 180, say fixing around two/three per active developer?
Dan.
