Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Received-SPF: neutral (herse.apache.org: 32.97.182.144 is neither permitted
 nor denied by domain of qozinx@gmail.com)
Message-ID: <457F40D9.4090603@gmail.com>
Date: Tue, 12 Dec 2006 15:52:57 -0800
From: Army <qozinx@gmail.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
 rv:1.7.1) Gecko/20040707
MIME-Version: 1.0
To: derby-dev@db.apache.org
Subject: Re: [VOTE] 10.2.2.0 release
References: <457DBB9D.5000704@sun.com>
In-Reply-To: <457DBB9D.5000704@sun.com>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit

Rick Hillegas wrote:
> Please download and test-drive the 10.2.2.0 candidate, then vote on 
> whether to accept it as a Derby release.

For posterity I ran a set of ODBC tests against "Derby Network Server - 10.2.2.0 
- (485682)" using the DB2 Runtime Client (v8) and all tests ran as expected.

I also ran the 10.2 "xmlSuite" [1] using ibm142 and the only diff was an 
expected diff in character counts that was mentioned in DERBY-1758 (and has been 
resolved as a testing issue in 10.3).

As an additional sanity check I put a 10.3 derbyTesting.jar in my classpath and 
then ran the JUnit "XMLSuite" against the 10.2.2 candidate jars--and all JUnit 
XML tests passed (I used ibm142).

So I vote +1 for the 10.2.2 candidate from an ODBC and XML perspective.
Army

--------

[1] The "xmlSuite" suite is not currently run as part of "derbyall" for 10.2, 
thus one must run the XML tests explicitly (after verifying that the required 
XML jars (JAXP and Xalan) are in the classpath):

 > java org.apache.derbyTesting.functionTests.harness.RunSuite xmlSuite