Rick Hillegas (JIRA) wrote:
It appears that fixing this bug will require us to agree on some mechanism for
caching VM-global Derby state. This seems to be an architectural decision which
requires careful thought and experiment. I think we should defer this to a
future release. I am moving this to 10.3 because thatt's the next release
available in the dropdown. I agree with Kathey that this is a good candidate
for a bug fix release in the 10.2 lineage.
Sounds like a reasonable move since there is no immediate solution
apparent. I was wondering though, could we could add a new version
that we can use as some of the 10.2 candidates start getting moved out?
I want to say 10.2.2.0 but am not sure that is right.
Kathey
