Return-Path: Delivered-To: apmail-forrest-dev-archive@www.apache.org Received: (qmail 76993 invoked from network); 17 Mar 2005 08:49:40 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 17 Mar 2005 08:49:40 -0000 Received: (qmail 87672 invoked by uid 500); 17 Mar 2005 08:49:39 -0000 Delivered-To: apmail-forrest-dev-archive@forrest.apache.org Received: (qmail 87626 invoked by uid 500); 17 Mar 2005 08:49:39 -0000 Mailing-List: contact dev-help@forrest.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@forrest.apache.org Delivered-To: mailing list dev@forrest.apache.org Received: (qmail 87606 invoked by uid 99); 17 Mar 2005 08:49:39 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: neutral (hermes.apache.org: local policy) Received: from ns3.wkwyw.net (HELO ns3.wkwyw.net) (217.199.181.91) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 17 Mar 2005 00:49:39 -0800 Received: (qmail 19329 invoked from network); 17 Mar 2005 08:49:38 -0000 Received: from 82-69-78-226.dsl.in-addr.zen.co.uk (HELO ?192.168.0.4?) (82.69.78.226) by ns3.wkwyw.net with SMTP; 17 Mar 2005 08:49:38 -0000 Message-ID: <4239449F.9020301@apache.org> Date: Thu, 17 Mar 2005 08:49:35 +0000 From: Ross Gardler User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@forrest.apache.org Subject: Re: planning for 0.7 release References: <20050222060249.GA25289@igg.indexgeo.com.au> <421B0011.4010704@apache.org> <20050226031147.GA15038@igg.indexgeo.com.au> <42200C0E.2060600@brondsema.net> <20050226072247.GA15251@igg.indexgeo.com.au> <20050317032949.GA21738@igg.indexgeo.com.au> In-Reply-To: <20050317032949.GA21738@igg.indexgeo.com.au> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N David Crossley wrote: > Let us get some planning happening or we are going to have trouble > getting the release out. > > We obviously missed the dates of 2003-03-25 and 2005-03-22 > because we need code-freeze and testing for one week beforehand. > > I suggest the following release plan: > > Code freeze and testing starts on 2005-03-30 which is > two days after Easter. During "code freeze" we cannot add any > new functionality, just bug fixes and documentation tweaks. > We create the release candidates for both Windows and UNIX on > this day and start the vote. > > If changes have been made during the week, then we create > another set of release candidates on 2005-04-05 to give people > time to verify the signatures and checksums and to do final tests. > > Actual release date Wednesday 2005-04-06 then wait 24 hours > for the mirrors to receive it before sending the announcements. > > If anyone wants any different, then please propose another > release plan. > I'm still snowed under with a project that keeps getting extended. It is due to finish (again) the end of this week. I'll do what I can but cannot be certain of my undivided attention. Ross