Table of Contents
Overview
The ![[WWW]](/wiki/modern/img/moin-www.png){kind=small}
Derby Overview provided by Jira shows issue counts and reports by component, issue type, developer, etc. Below are some additional reports for use in the Derby Project.
Jira Maintenance Reports
These reports assist with Jira Maintenance and help ensure that other reports are correct. In addition to developers periodically reviewing these reports for accuracy , it is helpful when logging and and updating issues to double check Status, Resolution, Affects Version, Fix Version, Priority, Component, Assignee, and Derby Info fields. Derby relies on community bug review (maintenance by individual developers) to keep Jira up to date.
|
All relevant Issues |
Personal View* |
Comments |
|
Most real Derby issues should have a Fix Version if marked fixed. Some that are external such as jvm issues may not |
||
|
Developers looking for bugs to fix often search on component. |
||
|
Keeping the component correct for fixed issues helps users searching for fixes and with accurate metrics |
||
|
Reporter or others should confirm the issue was fixed or resolved properly and close |
||
|
Affects version is important for differentiating outsanding product defects from those in the trunk and for users searching for defects in Jira |
||
|
If an issue is marked to be fixed in version X but nobody is assigned, maybe the Fix version or Assignee needs adjustment |
||
|
Please assign yourself to issues when submitting patches |
||
|
Make sure unresolved issues are still relevant |
* You must be logged into Jira to see the personal view.
Derby Project Reports
Reports to help Derby developers manage Jira Issues, patches, release notes, regression tests, etc.
|
Jira's Built In Overview of the project |
|
|
Patches submitted by derby developers awaiting review/commit. It is good to watch the aging on these patches to encourage contributors |
|
|
It is important to keep regression tests running cleanly. Ideally all known Regression Test Failures will be assigned |
|
|
Issues that might be appropriate for new developers. See also ForNewDevelopers |
|
|
These are changes that have been made or are proposed in the product that may have an unexpected impact on existing user applications |
|
|
Known outstanding regressions in the product. |
|
|
Issues needing a release note in an upcoming release |
|
|
All open code bugs including the trunk |
|
|
All open code bugs including the trunk grouped by component |
|
|
These are the critical issues that might hold up a release |
|
|
These are the bugs to which users are currently exposed. |
|
|
Issues that derby-users want fixed. |
|
|
All outstanding product improvement requests. (Does not include build and test) |
|
|
Known Security Issues and improvement requests |
|
|
Known performance issues and improvement requests |
|
|
Miscellaneous tasks. Often serious bugs are hiding here. |
Related Pages
HighValueFixCandidates Community bug analysis of issues that offer good return on time investment.