From derby-dev-return-34703-apmail-db-derby-dev-archive=db.apache.org@db.apache.org Sat Dec 16 06:42:34 2006 Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 84661 invoked from network); 16 Dec 2006 06:42:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Dec 2006 06:42:33 -0000 Received: (qmail 77799 invoked by uid 500); 16 Dec 2006 06:42:40 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 77578 invoked by uid 500); 16 Dec 2006 06:42:40 -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 77569 invoked by uid 99); 16 Dec 2006 06:42:40 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2006 22:42:39 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of mcintyre.a@gmail.com designates 66.249.92.173 as permitted sender) Received: from [66.249.92.173] (HELO ug-out-1314.google.com) (66.249.92.173) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 15 Dec 2006 22:42:29 -0800 Received: by ug-out-1314.google.com with SMTP id o2so1046526uge for ; Fri, 15 Dec 2006 22:42:08 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=Vqc4CYWXQipqLASNeuEUlsMEf7zhrZ5/7FEphw9I1JtjrM78uHljeUqpiJCR3mKnnxChbUaGHTDt8BxWxwsuzCLPCMM1m4GFa+K8ezKQuR4D+UlJ/BU8z1vTJYZUAn75PnIsAOkznD1D/O1yiyAsnQlTW1FmsJncevLaDSsSV7I= Received: by 10.78.97.7 with SMTP id u7mr769190hub.1166251328307; Fri, 15 Dec 2006 22:42:08 -0800 (PST) Received: by 10.78.138.7 with HTTP; Fri, 15 Dec 2006 22:42:08 -0800 (PST) Message-ID: <54ac72d70612152242s2a2bae62ie9cc69e2c764faf2@mail.gmail.com> Date: Fri, 15 Dec 2006 22:42:08 -0800 From: "Andrew McIntyre" To: derby-dev@db.apache.org Subject: Re: [VOTE] 10.2.2.0 release In-Reply-To: <457DBB9D.5000704@sun.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <457DBB9D.5000704@sun.com> X-Virus-Checked: Checked by ClamAV on apache.org On 12/11/06, 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. The candidate lives at: > > http://people.apache.org/~rhillegas/10.2.2.0/ > > The polls close at 5:00 pm San Francisco time next Monday, December 18. Verified all the signatures, checked the contents of each distribution, and ran tests on a couple of platforms (and yes, I copied the test jars into the same dir as the engine/net jars when running tests). Everything looked good. The contents of tools/jdbc4 are obviously no longer needed, but can be removed in some future release. I agree with Dan that the release notes' 'Issues' section is somewhat confusing, or at least confusingly titled. I think that maybe what is needed is an 'outstanding quality issues' vs. 'intentional changes in behavior' list. It seems to me that most of the content of the 'Issues' section are intentional, (hopefully-)positive changes in behavior of the engine, client, or tools. Calling these 'Issues' is at least a misnomer, and at worst misdirection, possibly leading a user to think that they may need to code around what are actually positive changes in Derby's behavior. Since the release notes may be the only piece of documentation long-time Derby users bother to review, it would be good to polish up these little bits of language to be more accurate. But, not worth holding up this release, anyway. So, on the whole, looks great. My vote: +1 andrew