Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 14400 invoked from network); 22 Jun 2006 19:38:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 22 Jun 2006 19:38:51 -0000 Received: (qmail 55373 invoked by uid 500); 22 Jun 2006 19:38:50 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 55337 invoked by uid 500); 22 Jun 2006 19:38:50 -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 55327 invoked by uid 99); 22 Jun 2006 19:38:50 -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 12:38:50 -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.143] (HELO e3.ny.us.ibm.com) (32.97.182.143) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 22 Jun 2006 12:38:49 -0700 Received: from d01relay04.pok.ibm.com (d01relay04.pok.ibm.com [9.56.227.236]) by e3.ny.us.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5MJcRjJ031092 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for ; Thu, 22 Jun 2006 15:38:28 -0400 Received: from d01av03.pok.ibm.com (d01av03.pok.ibm.com [9.56.224.217]) by d01relay04.pok.ibm.com (8.13.6/NCO/VER7.0) with ESMTP id k5MJcRC7270052 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 22 Jun 2006 15:38:27 -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 k5MJcRlM029856 for ; Thu, 22 Jun 2006 15:38:27 -0400 Received: from [127.0.0.1] (MARSDEN-IBM-LT1.usca.ibm.com [9.72.134.57]) by d01av03.pok.ibm.com (8.12.11.20060308/8.12.11) with ESMTP id k5MJcPPC029745 for ; Thu, 22 Jun 2006 15:38:27 -0400 Message-ID: <449AF1B0.3050005@sbcglobal.net> Date: Thu, 22 Jun 2006 12:38:24 -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 Development Subject: Re: Proposal for 10.2 release schedule References: <449AEAA7.8030109@sun.com> In-Reply-To: <449AEAA7.8030109@sun.com> Content-Type: text/plain; charset=us-ascii; 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 Rick Hillegas wrote: > The JCP requires that our JDBC4-exposing release can not be generally > available until the JDBC4 specification is finalized. Is this something that the Derby community is bound to? > > Here are proposed dates for 10.2 milestones: > > August 10 - Feature work committed. 10.2 branch created. > August 24 - Last day to commit changes for 10.2 > August 25 - Begin vetting 10.2 release candidate > September 15 - Target date for finishing the voting on Derby 10.2 What happens between September 15 and End of October on the 10.2 branch? Does bug fixing and work on 10.2.1 begin? If we fix critical bugs during that time in the 10.2 branch can't they go into the release end of October? > End of October - Expected GA of JDBC4 with Mustang > End of October - GA of Derby 10.2. Release promoted to Apache mirrors. > >