Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 32306 invoked from network); 15 Jun 2009 16:32:50 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 15 Jun 2009 16:32:50 -0000 Received: (qmail 4898 invoked by uid 500); 15 Jun 2009 16:33:00 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 4829 invoked by uid 500); 15 Jun 2009 16:33:00 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 4802 invoked by uid 99); 15 Jun 2009 16:33:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 15 Jun 2009 16:33:00 +0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=SPF_PASS,UNPARSEABLE_RELAY X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.136.44.57] (HELO smtp102.prem.mail.sp1.yahoo.com) (98.136.44.57) by apache.org (qpsmtpd/0.29) with SMTP; Mon, 15 Jun 2009 16:32:51 +0000 Received: (qmail 8444 invoked from network); 15 Jun 2009 16:32:29 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Received:X-Yahoo-SMTP:X-YMail-OSG:X-Yahoo-Newman-Property:Message-Id:From:To:In-Reply-To:Content-Type:Content-Transfer-Encoding:Mime-Version:Subject:Date:References:X-Mailer; b=FdB6d/EkjUfUc0lb5zz4amGa4qkW/3dZsFeEu+ihgBeG5BrxsnNBEVlM07HccVeqPWnY2NeuuMHTqNF30hDT2lZrEQpjcPoE2uMhLQvzJlLiJWaRowr1PnfFPSt/DhamTTZL1AuE8PbgXR0fPiEnuEeHY2phyeNKyWr6w2Fxlds= ; Received: from 076-076-148-215.pdx.net (david_jencks@76.76.148.215 with plain) by smtp102.prem.mail.sp1.yahoo.com with SMTP; 15 Jun 2009 09:32:28 -0700 PDT X-Yahoo-SMTP: .9oIUzyswBANsYgUm_5uPui0skTnzGJXJQ-- X-YMail-OSG: h0yeFXgVM1kc90SYlNKe42ARJFz7vaXJ3myMydoExrUQ3OpMsJ2S3dT_sIvYQSfdb2afMLwl3XMtItIJ3Th_vpOnc6X2jXg2YVWtHd.XI5DSjkP6SIcPMxW_aiOGJH0YEsdQklCPnUH7Q4bQvKlI1rJ5ZVdS1vlTKagwa8nz_sif1_rjO6ryf.hqfClyZ162cQsYnVY.NVaXEELFhBhlJt0S3nu7hQ56bq6dLSimoBAupyjnMXsB06t_KKEMQKWf86p3f3W29SwKN2Wl6.fLKexT3DFKsJf8Fla31DZQD6Qau.GodQ-- X-Yahoo-Newman-Property: ymail-3 Message-Id: <3B20F4F3-4908-4171-9057-20FAAB9F810B@yahoo.com> From: David Jencks To: dev@geronimo.apache.org In-Reply-To: <4A364264.8030706@apache.org> Content-Type: text/plain; charset=WINDOWS-1252; format=flowed; delsp=yes Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Apple Message framework v935.3) Subject: Re: Update the 2.2 release status page? Date: Mon, 15 Jun 2009 09:32:27 -0700 References: <4A364264.8030706@apache.org> X-Mailer: Apple Mail (2.935.3) X-Virus-Checked: Checked by ClamAV on apache.org I made some updates. I think I'm going to be the release manager =20 unless someone else volunteers. thanks david jencks On Jun 15, 2009, at 5:45 AM, Donald Woods wrote: > I saw discussions from David J. that he was planning on branching =20 > 2.2 any day now, so it seems that your targets are too far out. =20 > Also, we normally don't have a whole quarter between branching and =20 > releasing, but should be something like one month after a branch for =20= > the target release. > > > -Donald > > > Rex Wang wrote: >> HI >> I notice a user in mail list who complained that the = http://cwiki.apache.org/GMOxPMGT/geronimo-22-release-status.html=20 >> is out of date. >> >Ashwill, Steve (Facilities & Services) >> >Hello, >> >Can anyone tell me if there is a new roadmap in the works defining =20= >> a release schedule for version 2.2. We have been developing based =20= >> on the Geronimo 2.2 Release Status(OpenEJB 3.1), but if it will =20 >> >not be released in the next few months we may need to re-factor to =20= >> 2.1.4. Our support folks are a bit hesitant to deploy to =20 >> production using a snapshot version. I=92ve checked = http://cwiki.apache.org=20 >> >>>/GMOxPMGT/geronimo-22-release-status.html , but it has not been =20= >> updated in a while. >> >Any guessimation as to when and if 2.2 will be released would be =20 >> greatly appreciated. >> >Thanks, >> >Steve >> I think at least the dates following should update, can anyone help? >> Release Manager: >> Proposed Branch/freeze date: 12/12/08 1/9/09 1Q2009 -> 3Q2009 >> Proposed Release Candidate: 1/9/09 1/16/09 1Q2009 -> 4Q2009 >> Proposed Release date: 1/15/09 1/30/09 1Q2009 -> 4Q2009 >> -Rex