Bug triage for Derby 10.9

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

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

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

Issue Type

Assignee

Range

Completed

Store Bugs

mikem

all

thru 2/20/2012

Services Bugs

mikem

all

SQL Bugs

mamta

all

thru 2/24/2012

JDBC Bugs

mamta

all

thru 2/24/2012

Tools Bugs

mamta

all

thru 3/19/2012

Network Client Bugs

kmarsden

all

thru 2/20/2012

Network Server Bugs

kmarsden

all

thru 2/20/2012

Replication Bugs

Documentation Bugs

Test Bugs

mamta

DERBY-5638 thro DERBY-5663

thru 3/19/12

Build Tools Bugs

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

Issue Type

Assignee

Range

Completed

Store

Services

SQL

JDBC

Tools

Network Client

kmarsden

all

Network Server

kmarsden

all

Replication

Documentation

Test

Build Tools

Other Component

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_9 label to ones you review that stay open.

Tip: For issues that require no changes except the label, you can use bulk update to change the label without mail. First change the issues that need modification and add the label. Then chose "Return to previous screen" -> Tools -> Bulk update. From there you can select all and deselect particular ones where outstanding questions mean the label should not be updated yet. Select Edit -> Change Label and uncheck "Send Mail"

Issue Type

Assignee

Range

Completed

Store Bugs

mikem

all

Services Bugs

SQL Bugs

JDBC Bugs

Tools Bugs

Network Client Bugs

kmarsden

all

thru 2/20/2012

Network Server Bugs

kmarsden

all

thru 2/20/2012

Replication Bugs

Documentation Bugs

Test Bugs

Build Tools Bugs

Other Component Bugs