db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mike Matrigali <mikem_...@sbcglobal.net>
Subject Re: coming up
Date Mon, 10 Oct 2011 20:36:55 GMT
Great, I think it is time to have a new RC, given that a number
of blockers for the previous RC that was canceled have been checked in. 
  This way
everyone running tests can be using the same proposed release.

At this point I don't think the deadlock issues are worth holding
up a release for, though I would still hope they are high on
everyone's radar.

Does anyone consider anything in the current 10.8 branch a blocker
for a release at this time, assuming a RC made at this time passes
community testing?


Myrna van Lunteren wrote:
> Hi,
> Rick has backed out the fix for DERBY-4437.
> I'm running nstest on a couple of machines and - of course depending
> on the results in the next day or so - I hope to make a new candidate
> release on Monday, October 10, 2011.
> I'm not updating the wiki pages just yet...
> I believe most fixed bugs that are suitable for backport have been backported.
> I only have the following possibles:
> DERBY-3823 - NullPointerException in stress.multi test
>       The fix hasn't yet been checked in, but this might be nice to
> avoid this old intermittent test failure. Is this change suitable for
> backport or could it cause incompatibilities?
> DERBY-5427 - I think Kathey is on this. Would be nice to have, but it
> only affects ibm 1.7 users and only in specific situations.
> Any issues anyone is working on backporting?
> Regards,
> Myrna

View raw message