dasd asda wrote:
there is no progress on bug DERBY-790. I
am sure quite a few are running into this issue.
Please fastrack the resolution to this bug.
Hello dasd,
Thank you for bringing this issue onto the community radar. DERBY-790
is assigned but I think perhaps inactive at this time. I am cc'ing the
assigned developer directly so he can comment on whether that is the
case. I am also copying the original filer of the bug who indicated
that this was also a blocker in case they want to take action as well.
Regardless of whether an issue is assigned or not, if you need the fix
you should feel free to go ahead and submit a patch. Derby is an open
source project so we rely on folks who need functionality to jump in and
provide it themselves. It is great because you don't have to wait for
anybody, you can just fix it! A lot of people have worked hard to
refine our doc on the Wiki and elsewhere to make this easy. Please
take a look at:
http://wiki.apache.org/db-derby/?action=fullsearch&context=180&value=DerbyDev
If you don't want to make the change yourself, there are a few other
options to move the issue along.
1) Add a reproducible case to DERBY-790. Having a stand-alone,
working, java reproduction makes issues much more attractive to
developers picking up bugs.
2) Vote for the issue in Jira so it shows up on the popular issues.
DERBY-790 right now has 1 vote.
https://issues.apache.org/jira/browse/DERBY-790.
3) Do something for the community that will help in a general sense in
issue prioritization and throughput. For instance, you could start a
general discussion about how to address issues that have been assigned
for a long time but are not active.
4) Buy paid support. Some companies such as Sun and IBM offer paid
support options for their own packaging of Derby. You could try buying
support, but of course those support contracts never guarantee they will
fix your bug #:)
Hope this helps.
Kathey
