Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 28822 invoked from network); 23 Jun 2006 03:21:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jun 2006 03:21:12 -0000 Received: (qmail 27174 invoked by uid 500); 23 Jun 2006 03:21:11 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 26798 invoked by uid 500); 23 Jun 2006 03:21:10 -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 26781 invoked by uid 99); 23 Jun 2006 03:21:10 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 20:21:10 -0700 X-ASF-Spam-Status: No, hits=1.9 required=10.0 tests=DNS_FROM_RFC_ABUSE,DNS_FROM_RFC_POST X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Received: from [32.97.110.153] (HELO e35.co.us.ibm.com) (32.97.110.153) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 20:21:09 -0700 Received: from westrelay02.boulder.ibm.com (westrelay02.boulder.ibm.com [9.17.195.11]) by e35.co.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5N3Kmcd016314 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 22 Jun 2006 23:20:48 -0400 Received: from d03av02.boulder.ibm.com (d03av02.boulder.ibm.com [9.17.195.168]) by westrelay02.boulder.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k5N3KMcN273678 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 22 Jun 2006 21:20:23 -0600 Received: from d03av02.boulder.ibm.com (loopback [127.0.0.1]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k5N3KluW006165 for ; Thu, 22 Jun 2006 21:20:47 -0600 Received: from [127.0.0.1] (sig-9-76-200-15.mts.ibm.com [9.76.200.15]) by d03av02.boulder.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5N3KkM9006146 for ; Thu, 22 Jun 2006 21:20:47 -0600 Message-ID: <449B5E0D.1050800@sbcglobal.net> Date: Thu, 22 Jun 2006 20:20:45 -0700 From: Kathey Marsden User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.13) Gecko/20060414 X-Accept-Language: en-us, en MIME-Version: 1.0 To: derby-dev@db.apache.org Subject: Re: catch-22: Derby, Mustang, and JCP issue References: <449B3321.6080701@bristowhill.com> <449B4D5F.8070008@apache.org> <639B39E1-ED1D-437C-87DE-267D3EF92791@apache.org> In-Reply-To: <639B39E1-ED1D-437C-87DE-267D3EF92791@apache.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Brian McCallister wrote: > If the interfaces happen to exist in a release before the spec is final, > well, cool. Folks using them are at risk of the spec changing at the > last > minute, so I would put bright red warnings around them if they are event > documented before the official release of the spec (not of Derby). > +1 - We have a Derby 10.2 GA release with any JDBC 4.0 functionality marked as USE AT YOUR OWN RISK, just part of incremental devlopment and totally subject to change if the spec does. - Mustang takes that and runs with it. - Then we have a follow up release, yes even two months later where we are certified compliant. A nice clean 2 phase commit. I haven't read the legal stuff, but does this not work? Kathey