Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 2123 invoked from network); 9 Jul 2007 19:21:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 9 Jul 2007 19:21:12 -0000 Received: (qmail 48464 invoked by uid 500); 9 Jul 2007 19:21:15 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48239 invoked by uid 500); 9 Jul 2007 19:21:13 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 48230 invoked by uid 99); 9 Jul 2007 19:21:13 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 12:21:13 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [192.18.43.132] (HELO sca-es-mail-1.sun.com) (192.18.43.132) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 12:21:10 -0700 Received: from fe-sfbay-09.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l69JKngm021801 for ; Mon, 9 Jul 2007 12:20:49 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-09.sun.com by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JKX00301ER5T400@fe-sfbay-09.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Mon, 09 Jul 2007 12:20:49 -0700 (PDT) Received: from [10.7.250.155] by fe-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JKX00KMJF2NUUC0@fe-sfbay-09.sun.com> for derby-dev@db.apache.org; Mon, 09 Jul 2007 12:20:47 -0700 (PDT) Date: Mon, 09 Jul 2007 12:22:09 -0700 From: Rick Hillegas Subject: Re: 10.3 - to release or not to release? In-reply-to: <46925CC0.40309@gmail.com> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <46928AE1.90501@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT References: <46925CC0.40309@gmail.com> User-Agent: Thunderbird 1.5.0.5 (X11/20060828) X-Virus-Checked: Checked by ClamAV on apache.org Stanley Bradbury wrote: > Myrna van Lunteren wrote: >> Hi, >> >> I've been looking over the fixed and open bugs for the 10.3 release, >> and there is a lot of good stuff... >> >> However, there are also some worrying aspects: >> - There are a number of Critical bugs open, most without any >> indication of getting a fix. See: >> https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=10594&priority=2&resolution=-1 >> >> >> - There are a number of intermittent test regressions so we're not >> getting consistently clean test runs. Just look at the platform >> testing list to see this: >> http://wiki.apache.org/db-derby/TenThreePlatformTesting >> In addition, there are 7 items which never received any Buddy testing... >> Further, we still ran into a deterioration in the suites.All at one >> point, requiring running with extra memory on many systems, which was >> never addressed. >> >> - There are a largish number of open bugs, many of which are marked >> affects 10.3., i.e. affect the new functionality added with 10.3. >> >> On the other hand, it seems to me some of the current functionality, >> is eagerly awaited by the user community. A number of the critical >> bugs are not new with 10.3., or are related to security, which may, or >> may not affect a number of our users...And none of them have an >> owner... >> >> So, I intend to continue with my stated plan of generating a Release >> Candidate and call a vote next Monday, but I would suggest we plan for >> a bug fix release off the 10.3 branch to specifically drive down the >> number of bugs... >> >> Thx, >> Myrna >> > Hi Myrna - > Thanks for the through release report. I took a look at the critical > bug list and am concerned about the regression that causes locking > problems: DERBY-2892 > - this is a > regression of the DERBY-255 fix and, though it was introduced in 10.2, > should be addressed quickly. Has anyone look at the checkin that > might have caused the regression? > DERBY-326 (svn 405037). If someone volunteers to scratch this itch imminently, then I think we should consider delaying the release. Otherwise, I would not let this 10.2 bug gate the release of other quality improvements. Hopefully this issue will find a champion soon or at least in time for the 10.3 maintenance release. Regards, -Rick