Do we have an estimate in turn of how long it takes to fix DERBY-4331 and knowledge in turn whether the fix will cause any further regression? I just want to make sure we iron out some of the unknown issues. Thanks, Lily
________________________________ From: Rick Hillegas <[email protected]> To: [email protected] Sent: Monday, August 3, 2009 7:58:40 AM Subject: Re: DERBY-4331 and the 10.5.2.0 release Knut Anders Hatlen wrote: > Rick Hillegas <[email protected]> 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 >> 10.5.2.0 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 10.5.2.0, 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. :( > >
