Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 95731 invoked from network); 13 Sep 2006 19:02:47 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 13 Sep 2006 19:02:47 -0000 Received: (qmail 96714 invoked by uid 500); 13 Sep 2006 19:02:46 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 96689 invoked by uid 500); 13 Sep 2006 19:02:46 -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 96680 invoked by uid 99); 13 Sep 2006 19:02:46 -0000 Received: from idunn.apache.osuosl.org (HELO idunn.apache.osuosl.org) (140.211.166.84) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 13 Sep 2006 12:02:46 -0700 Authentication-Results: idunn.apache.osuosl.org smtp.mail=Richard.Hillegas@Sun.COM; spf=permerror X-ASF-Spam-Status: No, hits=0.0 required=5.0 tests= Received-SPF: error (idunn.apache.osuosl.org: domain Sun.COM from 192.18.42.249 cause and error) Received: from ([192.18.42.249:65112] helo=nwkea-pix-1.sun.com) by idunn.apache.osuosl.org (ecelerity 2.1 r(10620)) with ESMTP id 89/00-10750-89558054 for ; Wed, 13 Sep 2006 12:02:59 -0700 Received: from d1-sfbay-09.sun.com ([192.18.39.119]) by nwkea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k8DJ1O8X013229 for ; Wed, 13 Sep 2006 12:01:24 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-09.sun.com by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J5J00901OPPTH00@d1-sfbay-09.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Wed, 13 Sep 2006 12:01:24 -0700 (PDT) Received: from [129.144.89.163] by d1-sfbay-09.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J5J00GXPOUC7X2A@d1-sfbay-09.sun.com> for derby-dev@db.apache.org; Wed, 13 Sep 2006 12:01:24 -0700 (PDT) Date: Wed, 13 Sep 2006 12:01:31 -0700 From: Rick Hillegas Subject: Re: Doc notice for JDBC 4 functionality in Derby 10.2 In-reply-to: <4508512C.1090302@bristowhill.com> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <4508558B.7070808@sun.com> MIME-version: 1.0 Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 7BIT X-Accept-Language: en-us, en References: <45084177.8020701@bristowhill.com> <450842E7.2030709@bristowhill.com> <45084E8A.4080400@sun.com> <4508512C.1090302@bristowhill.com> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Hi Jean, This sounds fine. I was planning on highlighting the license issue in the Release Notes anyway. Regards, -Rick Jean T. Anderson wrote: >how's this for consolidating yours and mine latest: > >This documentation references new JDBC 4.0 functionality that is not >enabled in this Apache Derby 10.2 release because a final Java SE 6 >release was not available when this release was produced. JDBC 3.0 will >be available by default when used with a Java SE 6 virtual machine. JDBC >4.0 functionality will only be available to developers who download Java >SE 6 themselves and with it build Derby's optional JDBC 4.0 support. >Please see the Release Notes for details on how to build this optional >JDBC 4.0 functionality. ***Please also note the licensing restrictions >which limit your use of beta versions of Java SE 6. The beta JDK may >only be used for evaluation purposes; the same restriction applies to >Derby's JDBC 4.0 support when built using the beta version of Java SE 6.*** > >Can we move the portion I highlighted with *** into the release notes >since developers will have to look at that info to understand how to >build in jdbc 4? --I don't think we need to be in the business of >educating users on the license in the reference guide pages I want to >update. > > -jean > > >Rick Hillegas wrote: > > >>Hi Jean, >> >>This looks great. I'd like to roll up David's observation and tweek this >>a bit more: >> >>This documentation references new JDBC 4.0 functionality that is not >>enabled in this Apache Derby 10.2 release because a final Java SE 6 >>release is not available yet. JDBC 3.0 will be available by default when >>used with Java SE 6. JDBC 4.0 functionality will only be >>available to developers who download Java SE 6 themselves and >>with it build Derby's optional JDBC 4.0 support. Please see the Release >>Notes >>for details on how to build this optional JDBC 4.0 functionality. >>Please also note the licensing restrictions which limit your use >>of beta versions of Java SE 6. The beta JDK may only be used for >>evaluation purposes; the same restriction applies to Derby's >>JDBC 4.0 support when built using the beta version of Java SE 6. >> >> >>Thanks, >>-Rick >> >>Jean T. Anderson wrote: >> >> >> >>>Scratch that first attempt -- already caught an ambiguity. Second try: >>> >>>This documentation references new JDBC 4.0 functionality that is not >>>enabled in this Apache Derby 10.2 release because a final Java SE 6 >>>release is not available yet. JDBC 3.0 will be available by default when >>>used with a Java SE 6 beta build. JDBC 4.0 functionality will only be >>>available to developers who download Java SE 6 themselves and build >>>Derby with it. >>> >>>-jean >>> >>>Jean T. Anderson wrote: >>> >>> >>> >>> >>>>I'm looking for wording we can plug into both the release notes and >>>>strategic pages in the documentation. How does this sound? >>>> >>>> >>>>This documentation references new JDBC 4.0 functionality that is not >>>>enabled in this Apache Derby 10.2 release. Until a final Java SE 6 >>>>release is available, JDBC 3.0 will be available by default when used >>>>with a Java SE 6 beta build. JDBC 4.0 functionality will only be >>>>available to developers who download Java SE 6 themselves and build >>>>Derby with it. >>>> >>>>tweaks? comments? corrections? >>>> >>>>thanks, >>>> >>>>-jean >>>> >>>> >>>> >>> >>> >>> >>> > > >