Table of Contents
About this page
Normally users indicate which bugs they would like to see fixed using the Jira Vote mechanism. (The issues with the most votes can be seen here). This Wiki page is where members of the development community and those involved in support and QA can list fixes that they see as giving a potentially high return on time investment based on:
- Frequency and likelihood the issue might be hit by users.
- Estimated difficulty of fix.
- Risk to existing users if the fix is implemented.
- Severity of the issue.
- Availability of a workaround.
- The amount of user/developer time is wasted by the issue.
High Value Bug Fixing Candidates
High value fix candidates are marked by the community by checking the "High Value Fix" category in Jira. See High Value Fix Candidates in Jira. These are issues that would be great to see fixed for the next release. For other ideas see the full list of Derby Open Code Bugs, Regression Test Failures and Open Product Regressions
High value is also placed on issues which have severe consequences for users. The following descending level of severity has been found useful in 10.6 and later releases: