db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Myrna van Lunteren <m.v.lunte...@gmail.com>
Subject Re: Java DB, was: DERBY-4331 and the release
Date Wed, 05 Aug 2009 16:35:55 GMT
On Wed, Aug 5, 2009 at 8:33 AM, Rick Hillegas<Richard.Hillegas@sun.com> wrote:
> Just a heads-up and a request for the community's patience:
> Normally, the Java DB team produces a re-spin of every Derby release. The
> Java DB team has discussed the impending announcement and we have
> decided that there is too much risk for us in re-spinning this release. We
> believe that customers affected by DERBY-3926 have largely figured out how
> to work around that problem because the bug has been in Derby since 10.1. In
> contrast, the implications of DERBY-4331 are not understood.
> However, we have customers who want other fixes which are in the 10.5
> branch. We would like to produce a Java DB distribution which would
> be the state of the 10.5 branch without DERBY-3926. What we propose to do is
> the following:
> 1) Back out DERBY-3926 on the 10.5 branch.
> 2) Produce a distribution from the branch at that point.
> 3) Put DERBY-3926 back into the 10.5 branch.
> We would like to warn the community that we are going to do this and ask for
> your patience while we produce this distribution.
> Thanks,
> -Rick

I wonder - will you be bumping the version number? I think the
community decided it was ok to do so for any committer feeling the


View raw message