The above 2 mentioned links for issues seem to be not working since it has a
private access.
Hmmm... I'm not quite sure what's wrong there. JIRA permissions are a little
bit odd. Possibly I have to add you to the "derby developers" group in JIRA.
What is your JIRA ID?
I just have built the code base. Can u give some minor issues so that I can get
the confidence. Is the issue in the following link is ok to start up with?
https://issues.apache.org/jira/browse/DERBY-6863
DERBY-6863 is definitely an important bug, and it would be wonderful
to get somebody working on it.
However, I worry that it is a pretty hard bug, not so much conceptually
hard, but hard because it requires working in some of the parts of Derby
that aren't terribly easy to understand.
In particular, Derby implements some of the SQL execution processing
by generating Java bytecode at runtime, and when that bytecode is
generated incorrectly, figuring out why can be very challenging.
But, by all means, if DERBY-6863 is interesting to you, then it definitely
needs to be fixed!
If you are looking for some simpler bugs to work on, just to get some
practice with the different pieces of Derby, and how the code fits
together, and how to add new tests and run existing tests, try these:
https://issues.apache.org/jira/browse/DERBY-6752
https://issues.apache.org/jira/browse/DERBY-546
https://issues.apache.org/jira/browse/DERBY-693
https://issues.apache.org/jira/browse/DERBY-5852
thanks,
bryan
