db-derby-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Db-derby Wiki] Update of "DerbyTenEightOneBugTriage" by KatheyMarsden
Date Thu, 10 Feb 2011 00:21:29 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Db-derby Wiki" for change notification.

The "DerbyTenEightOneBugTriage" page has been changed by KatheyMarsden.


New page:
= Bug triage for Derby 10.8.1 =

/!\ Under Construction /!\

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.

== Untriaged issues ==

||Issue Type  || Assignee || Completed ||
|| || || ||
|| [[https://issues.apache.org/jira/sr/jira.issueviews:searchrequest-printable/temp/SearchRequest.html?jqlQuery=project%3DDERBY+AND+Resolution+%3D+Unresolved+and+Urgency+is+EMPTY+and+COMPONENT+%3D+Store+AND+KEY+%3C++DERBY-2500&tempMax=1000
| Never triaged Store Bugs under DERBY-2500]] ||  ||  ||

View raw message