Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 87598 invoked from network); 23 Jun 2006 17:55:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 23 Jun 2006 17:55:40 -0000 Received: (qmail 45536 invoked by uid 500); 23 Jun 2006 17:54:54 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 42869 invoked by uid 500); 23 Jun 2006 17:54:42 -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 41686 invoked by uid 99); 23 Jun 2006 17:54:31 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jun 2006 10:54:31 -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.182.144] (HELO e4.ny.us.ibm.com) (32.97.182.144) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 23 Jun 2006 10:32:53 -0700 Received: from d01relay02.pok.ibm.com (d01relay02.pok.ibm.com [9.56.227.234]) by e4.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5NHWWhI005618 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Fri, 23 Jun 2006 13:32:32 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay02.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k5NHWVdx287262 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Fri, 23 Jun 2006 13:32:32 -0400 Received: from d01av03.pok.ibm.com (loopback [127.0.0.1]) by d01av03.pok.ibm.com (8.12.11.20060308/8.13.3) with ESMTP id k5NHWVSG028534 for ; Fri, 23 Jun 2006 13:32:31 -0400 Received: from [127.0.0.1] (sig-9-76-200-15.mts.ibm.com [9.76.200.15]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5NHWUmB028472 for ; Fri, 23 Jun 2006 13:32:31 -0400 Message-ID: <449C25AC.3030903@sbcglobal.net> Date: Fri, 23 Jun 2006 10:32:28 -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> <449B5B49.5040601@pobox.com> <449B7BD6.8030601@apache.org> <54ac72d70606222332w75f301f2y627f3ac97fa68017@mail.gmail.com> <449C1BE6.9010903@sun.com> In-Reply-To: <449C1BE6.9010903@sun.com> 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 David Van Couvering wrote: > > What happened to the proposal to vote and approve a GA-enabled > release, but not make it actually available until Java SE 6 goes GA? > Did we decide this was not feasible? I may have missed it, but I > don't think I saw that discussion anywhere. > This was my comment regarding my concerns about this dependency. http://www.nabble.com/Re%3A-catch-22%3A-Derby%2C-Mustang%2C-and-JCP-issue-p5012231.html I think from a community perspective we would like other new projects to look at us as a good example. Will they say Yes! Let's do it just like Derby: - Wait more than a year for our first feature release, - Make pseudo GA release and ask our Release Manager to hold onto it until the company he works for releases their comercial product that uses it. - Set a precedent for external comercial dependencies on our release criteria. I think/hope they won't. Kathey