Bug triage for Derby 10.8.1

Our last bug triage was for 10.5.2 (see DerbyTenFiveTwoBugTriage ) , so it is time to take a comprehensive look at the bugs again. Below are links to the untriaged bugs for 10.8, those that do not have the derby_triage10_8 label. After triaging issues please add this label.

So, for each open code issue, we should at least consider the following items:

• For bugs, check if it is really an Improvement
• That Components look correct.
• Validate Urgency (no open issue should have None in this field)
• Verify and check-boxes in Issue and fix info section. Consider if this is a newcomer issue.
• Evaluate and verify existing check-boxes in Bug behavior facts.
• Consider issues for closing, if no repro exists and it is old (more than half a year). If filed by a user, I think we should ask for feed-back before we close.
• add the label derby_triage10_8 to the issue.

Note: as issues are triaged, they will come off the lists queries below. We are done when the lists are empty. I tried to make the initial chunks less than 50 issues and putting them in meaningful categories.

The guidelines for the various fields in Jira are outlined here. Please check fields for accuracy and be sure to mark the urgency and add the label derby_triage10_8 for issues you triage. When you assign yourself, fill in the range column if you wish to take on part of the list.

Never Triaged Bugs

Never Triaged Non-Bugs

These are marked Improvements, Enhancements and Sub-tasks. In addition to the normal triage, check that they should not be marked as bugs.

Previously Triaged Bugs

These were triaged for 10.5.2 in Summer 2009. Make sure they are still relevant and close them if they have been fixed by another issue or are clearly not reproducible based on the information provided. Please add the derby_triage10_8 label to ones you review that stay open.