Ok, it seems to be amicable then that we need to abort.

We can go on with Rick as the release manager and get this fixed for a, skipping altogether. I'm still under my GSoC period but I'm available to help with whatever has to be done. I would gladly offer to fix this issue but it feels like 'a little too much sand for my truck' and it would probably take me way too long and way too much of banging my head on the wall, so I'm leaving it up to someone more experienced than me.


On Mon, Aug 3, 2009 at 3:58 PM, Rick Hillegas <Richard.Hillegas@sun.com> wrote:
Knut Anders Hatlen wrote:
Rick Hillegas <Richard.Hillegas@Sun.COM> writes:

As I see it, data corruptions are the worst kind of database bug,
followed closely by wrong results. We have a precedent for pulling
releases from our download site and I recommend that we pull the release because of this regression.

Although we have pulled releases with serious problems from our download
site once, I think we shouldn't make that the rule. The pulling did
cause some problems for us, like holes in the release notes when
upgrading over multiple releases in one go.
Note that there won't be a hole in the release notes in this case.

And most of the releases
from the 10.3 and 10.4 branches did have wrong results regressions, but
they're still available for download.
Probably we would have spun new RCs for those distributions if our release testing had disclosed the regressions early on.

However, since we haven't yet announced, holding the
announcment (possibly pulling the release from the download page) and
quickly re-spinning a release with DERBY-4331 fixed sounds like a good
option. Also, I'd prefer a quick re-spin as soon as the known
regressions are fixed, rather than having a new maintenance release in
the autumn, since right now all our 10.5 releases have known regressions
from 10.4.

That said, I won't be able to help with a release the next two weeks, so
I'm just expressing a wish for a quick fix, not actually offering to do
the work. :(