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 10.5.2.0 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 10.5.2.1 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
Kathey Marsden wrote:
Rick Hillegas wrote:
It seems to me that the reactions to this email thread were mostly
negative.
It is hard to tell without a formal vote (which of course would take a
week) but I see a more mixed reaction on the issue of posting the
release. Some people say complete the release process, some say
abort and others think we should just stay in limbo a bit longer to
research impact. I don't think there is a clear consensus. There
also seems to be a similar divergence of opinions on whether and where
to back out the DERBY-3926 fix.
As Knut mentioned we have left releases with known wrong results
regressions on the site before without even a mention of the problem
on the download page. I feel like as release manager I should make a
decision soon and there is not time for a 7 day revote on 10.5.2.0.
My inclination is to go ahead with the process and include the warning
on the download page.
Then there can be more discussion and/or a vote on the fate of the
current DERBY-3926 fix, separate from the release discussion.
Kathey
