Re: FYI - Derby open code bugs chart

[Rick Hillegas <Ri...@Sun.COM>]

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.
>

Re: FYI - Derby open code bugs chart

[Daniel John Debrunner <dj...@apache.org>]

Rick Hillegas wrote:
> This sounds like a good idea. Some of these bugs have been fixed but not 
> closed.

The filter only reports bugs that are: Open, In Progress and Reopened.

> 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.

Closed or Resolved? I think the expected behaviour is that if the 
contributor/committer fixes the bug then they mark it as resolved. The 
reporter then should mark it as closed (or re-open it).

http://db.apache.org/derby/DerbyBugGuidelines.html#%22Close%22+your+bug+once+it+is+%22Resolved%22

Dan.

> It might be good for people to review the bug reports they have 
> opened to see if some of them can be closed now.

Re: FYI - Derby open code bugs chart

[Rick Hillegas <Ri...@Sun.COM>]

Thanks, Kathey!

Kathey Marsden wrote:
> Rick Hillegas wrote:
>>  It might be good for people to review the bug reports they have 
>> opened to see if some of them can be closed now.
>>
> Here is the link to issues you opened that have been resolved but not 
> closed.
> http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&status=5&reporterSelect=issue_current_user&sorter/field=issuekey&sorter/order=DESC 
>
>
>
> This and other maintenance reports are available at:
> http://wiki.apache.org/db-derby/DerbyJiraReports
>

Re: FYI - Derby open code bugs chart

[Kathey Marsden <km...@sbcglobal.net>]

Rick Hillegas wrote:
>  It might be good for people to review the bug reports they have 
> opened to see if some of them can be closed now.
>
Here is the link to issues you opened that have been resolved but not 
closed.
http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10594&status=5&reporterSelect=issue_current_user&sorter/field=issuekey&sorter/order=DESC


This and other maintenance reports are available at:
http://wiki.apache.org/db-derby/DerbyJiraReports