Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 6092 invoked from network); 12 Sep 2006 23:20:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Sep 2006 23:20:05 -0000 Received: (qmail 48754 invoked by uid 500); 12 Sep 2006 23:20:04 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 48721 invoked by uid 500); 12 Sep 2006 23:20:04 -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 48712 invoked by uid 99); 12 Sep 2006 23:20:04 -0000 X-ASF-Spam-Status: No, hits=0.5 required=10.0 tests=DNS_FROM_RFC_ABUSE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of scotsmatrix@gmail.com designates 66.249.92.169 as permitted sender) Received: from [66.249.92.169] (HELO ug-out-1314.google.com) (66.249.92.169) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Sep 2006 16:20:04 -0700 Received: by ug-out-1314.google.com with SMTP id m2so1911579uge for ; Tue, 12 Sep 2006 16:19:42 -0700 (PDT) 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=pXx1bI31EY4BolkF5AXnTqxs4IyA83IbsW/VEjo7OrbNC+fsh5KedS9y/eBR/dh1OztLaL/RUroGU99UGwffzzBTYYVrfcD/A7ooFZQ3jgcISSRJEsFiCSO5hwm5dxNZovb95cen3AqKFLd0yEJBkY6i71fdphu/+/iG2qO0i1I= Received: by 10.66.244.10 with SMTP id r10mr3727685ugh; Tue, 12 Sep 2006 16:19:42 -0700 (PDT) Received: by 10.66.255.1 with HTTP; Tue, 12 Sep 2006 16:19:42 -0700 (PDT) Message-ID: <9f40b500609121619h207c6840uf07b38167ee02bc5@mail.gmail.com> Date: Tue, 12 Sep 2006 16:19:42 -0700 From: "Laura Stewart" To: derby-dev@db.apache.org Subject: Re: 10.2 plans (was Re: 10.2 licensing issue) In-Reply-To: <4506FE32.8090601@apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <54ac72d70609111802w1f123022u92f8a9a0cec05425@mail.gmail.com> <45065468.7080009@gmail.com> <4506C026.6080607@mtrad.com> <4506CF63.90507@gmail.com> <4506ECCA.10509@sun.com> <4506FE32.8090601@apache.org> X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N On 9/12/06, Daniel John Debrunner wrote: > > In both cases the current state of the 10.2 branch is left unchanged wrt > JDBC 4.0, ie. no removal of JDBC 4.0 from code or documentation. > > Dan. > > If either of these approaches are used, the doc issue needs to be handled carefully. The JDBC 4.0 information will be in the documentation. Even if a statement is put into the Release Notes about this, it is very likely that a user (or 2) will miss the statement about JDBC 4.0 in the Release Notes and run into some problems. Something should also be posted on the Web Pages for Derby as well. I am not entirely comfortable with leaving a feature in the documentation that is not being delivered. If the docs are left as is, then I would prefer a feature release 10.3 when we formally support JDBC 4.0. -- Laura Stewart