I wasn't sure who should CLOSE a bug once it is fixed. According to the URL, it seems submitter should be closing the bug after verifying the fix. But may be, at the release time, it makes sense to close long pending bugs that need to be closed. Some guidelines on the matter would be nice, so everyone does the same...

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



"As the submitter of a bug, it is your responsibility to verify a bug fix and "Close" the issue. Once fixed, a developer marks the bug as "Resolved" with a resolution of "Fixed". You need to then go back and "Close" the issue, provided you agree the bug has been fixed. If the resolution of the bug is something other than "Fixed" and you disagree, or the fix submitted did not really resolve the issue, you need to "Reopen" the issue. Please add relevant comments in Jira when doing these operations. See the document titled Filing Apache Derby Issues in Jira for additional details."

Satheesh

Andrew McIntyre wrote:
I am conducting a review of the bugs that are marked as resolved in  JIRA but are not yet closed. It would be helpful if the people listed  below could review the items under their name and close the issue  with the appropriate Fix version if the issue has been fixed. I have  included a link to the JIRA issue below, along with the person that I  think should review the issue and my guess as to what should be done  with the issue.

Bernt:
http://issues.apache.org/jira/browse/DERBY-320 - close as fixed in  10.1.0.0

Dan:
http://issues.apache.org/jira/browse/DERBY-19 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-30 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-62 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-72 - close as fixed in  10.0.2.1 (or Jeremy)
http://issues.apache.org/jira/browse/DERBY-74 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-83 - close as fixed in  10.0.2.1 (or Jeremy)
http://issues.apache.org/jira/browse/DERBY-109 - close as duplicate  of DERBY-176 (or Barnet Wagman)
http://issues.apache.org/jira/browse/DERBY-130 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-225 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-325 - close as fixed in  10.1.0.0 (or Dibyendu)

David:
http://issues.apache.org/jira/browse/DERBY-214 - close as fixed in  10.1.0.0

Jack:
http://issues.apache.org/jira/browse/DERBY-6 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-14 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-127 - close as fixed in  10.1.0.0

Jean:
http://issues.apache.org/jira/browse/DERBY-9 - reopen as doc issue  for 10.1.0.0
http://issues.apache.org/jira/browse/DERBY-41 - reopen as doc issue  for 10.1.0.0
http://issues.apache.org/jira/browse/DERBY-58 - reopen as doc issue  for 10.1.0.0
http://issues.apache.org/jira/browse/DERBY-87 - close as fixed in  10.1.0.0 DITA docs

Jeff:
http://issues.apache.org/jira/browse/DERBY-52 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-116 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-164 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-168 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-181 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-199 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-227 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-234 - close as fixed in  10.1.0.0

Kathey:
http://issues.apache.org/jira/browse/DERBY-10 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-61 - close and link to  DERBY-204
http://issues.apache.org/jira/browse/DERBY-67 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-250 - close as fixed in  10.1.0.0

Lance:
http://issues.apache.org/jira/browse/DERBY-242 - close as fixed in  10.1.0.0

Mamta:
http://issues.apache.org/jira/browse/DERBY-124 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-189 - close as fixed in  10.1.0.0

Myrna:
http://issues.apache.org/jira/browse/DERBY-44 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-45 - close as fixed in  10.0.2.1

Satheesh:
http://issues.apache.org/jira/browse/DERBY-21 - close as fixed in  10.0.2.1 (or Amit Handa)
http://issues.apache.org/jira/browse/DERBY-25 - close as duplicate of  DERBY-3
http://issues.apache.org/jira/browse/DERBY-50 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-59 - close as fixed in  10.0.2.1 (or Jon Craven)

Shreyas:
http://issues.apache.org/jira/browse/DERBY-33 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-63 - close as duplicate of  DERBY-99
http://issues.apache.org/jira/browse/DERBY-95 - close as fixed in  10.1.0.0

Sunitha:
http://issues.apache.org/jira/browse/DERBY-42 - close as fixed in  10.0.2.1
http://issues.apache.org/jira/browse/DERBY-198 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-236 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-265 - close as fixed in  10.1.0.0

Suresh:
http://issues.apache.org/jira/browse/DERBY-96 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-101 - close as fixed in  10.1.0.0
http://issues.apache.org/jira/browse/DERBY-235 - close as fixed in  10.1.0.0

Thanks!

andrew



Reply via email to