Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 97686 invoked from network); 27 Jun 2006 19:13:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 27 Jun 2006 19:13:13 -0000 Received: (qmail 38332 invoked by uid 500); 27 Jun 2006 19:13:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 38307 invoked by uid 500); 27 Jun 2006 19:13:12 -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 38298 invoked by uid 99); 27 Jun 2006 19:13:12 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 12:13:12 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [192.18.42.249] (HELO nwkea-pix-1.sun.com) (192.18.42.249) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 27 Jun 2006 12:13:11 -0700 Received: from d1-sfbay-02.sun.com ([192.18.39.112]) by nwkea-pix-1.sun.com (8.13.6+Sun/8.12.9) with ESMTP id k5RJComj027334 for ; Tue, 27 Jun 2006 12:12:50 -0700 (PDT) Received: from conversion-daemon.d1-sfbay-02.sun.com by d1-sfbay-02.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) id <0J1J0070194K7400@d1-sfbay-02.sun.com> (original mail from Richard.Hillegas@Sun.COM) for derby-dev@db.apache.org; Tue, 27 Jun 2006 12:12:50 -0700 (PDT) Received: from [129.150.32.241] by d1-sfbay-02.sun.com (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPSA id <0J1J00MJF9DESS70@d1-sfbay-02.sun.com> for derby-dev@db.apache.org; Tue, 27 Jun 2006 12:12:50 -0700 (PDT) Date: Tue, 27 Jun 2006 12:13:00 -0700 From: Rick Hillegas Subject: Re: Wrapping up coding for 10.2 In-reply-to: <44A177B9.6040202@sbcglobal.net> Sender: Richard.Hillegas@Sun.COM To: derby-dev@db.apache.org Message-id: <44A1833C.6050407@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: <44A02DE8.6030908@sun.com> <44A177B9.6040202@sbcglobal.net> User-Agent: Mozilla Thunderbird 1.0.6 (Windows/20050716) X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Thanks, Mike. Here's a potential schedule of release candidates. Is this unorthodox or too aggressive? Could you propose a more realistic schedule? August 10 : Create branch and generate snapshot for testing August 24 : Generate first release candidate August 31 - September 7 : Generate second release candidate September 15 : If necessary generate third release candidate with hopefully quick vetting Regards, -Rick Mike Matrigali wrote: > august 10th seems fine for me. Your schedule does not talk in terms of > release candidates. I am ok with a code complete on august 10th and > assuming a rc1 is created on august 10th it seems pretty aggressive to > have all testing and all fixes from that testing in a final rc 2 weeks > later. It seems like we needed more time than that for a point release > from a stable branch, seems likely that this new branch will take longer. > > Rick Hillegas wrote: > >> I hate to be a nudge, but I didn't get a response when I asked this >> question last week: Do we expect to be done with development for 10.2 >> by August 10? >> >> I expect that the JDBC4 work will have wrapped up by then. Besides >> the JDBC4 effort, 10.2 is waiting for feature work from Army, Dan, >> and Satheesh. Do you guys think you'll be done by August 10? >> >> If anyone else is working on 10.2 features, could you let us know >> whether August 10 sounds like a reasonable date for cutting a release >> branch? >> >> Thanks, >> -Rick >> >> >