Rick Hillegas wrote:
we will revisit all of the Blocker/Critical bugs which we've marked
for 10.2.
Yes, priorities (mental translation SEVERITIES) are quite out of whack,
not only because of the misnamed field, but because "Major" is the default.
After we get Urgency in and all the fields documented based on recent
discussions. In addition to our distributed maintenance process, we
really need a full pass of Jira Issue's open and closed. We should
correct Jira settings for regression, existing application impact,
Priority, affects and Fix version (for closed issues), and release note
needed. These should all be fairly objective fields.
If you are a newcomer, student or other who wants to make a high
value contribution and learn a lot about Derby in the process and start
working with me on this important project, I would be most grateful.
Best qualified candidates would be someone with
- An intense focus on the user perspective or desire to have it.
- A high level of respect and appreciation for the developers who add
all the wonderful new functionality and fix the bugs.
- Enough of the two items listed above to get excited when you find a
hidden issue because flushing out and identifying issues *before* users
hit them is what everyone wants.
- Some JDBC API /Database externals (usage) knowledge but not
absolutely required.
Please let me know if you are interested.
Kathey
