Hi Bryan,
I think I would like to not check in any more feature work for 10.2.
Instead, I'd like to just focus on stabilizing the beta. Do you think
that you could hold off committing this work until at least Monday? That
would give me time to mega-merge the trunk to the 10.2 branch on Friday.
After that point, we could start swimming with lead weights on and make
sure that each patch is inidividually committed to both the trunk and to
the 10.2 branch.
Thanks,
-Rick
Bryan Pendleton wrote:
Hi,
I think we're getting close to the point where DERBY-119 is ready for
commit. It's been tested and reviewed by several people (thanks!) and
seems to be behaving well. Here's the link for convenience:
http://issues.apache.org/jira/browse/DERBY-119
However, since this is a new feature, I'm concerned that I don't want
a commit of this feature to jeopardize the 10.2 release.
Is there anything special I should consider? Should I hold off on the
commit for a few weeks to give 10.2 a bit more time to stabilize?
thanks,
bryan
P.S. I'm hoping that DERBY-1491 would not be far behind, as its
implementation shares a lot of infrastructure with DERBY-119.
