Return-Path: Delivered-To: apmail-geronimo-dev-archive@www.apache.org Received: (qmail 81142 invoked from network); 26 Feb 2006 09:31:59 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 26 Feb 2006 09:31:59 -0000 Received: (qmail 15978 invoked by uid 500); 26 Feb 2006 09:31:47 -0000 Delivered-To: apmail-geronimo-dev-archive@geronimo.apache.org Received: (qmail 15913 invoked by uid 500); 26 Feb 2006 09:31:47 -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 15902 invoked by uid 99); 26 Feb 2006 09:31:47 -0000 Received: from asf.osuosl.org (HELO asf.osuosl.org) (140.211.166.49) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Feb 2006 01:31:47 -0800 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_HELO_PASS X-Spam-Check-By: apache.org Received-SPF: pass (asf.osuosl.org: local policy) Received: from [63.208.196.171] (HELO outbound.mailhop.org) (63.208.196.171) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 26 Feb 2006 01:31:46 -0800 Received: from 0x5731d32c.bynxx15.adsl-dhcp.tele.dk ([87.49.211.44] helo=[192.168.1.46]) by outbound.mailhop.org with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.51) id 1FDIFR-000Fj8-Gk for dev@geronimo.apache.org; Sun, 26 Feb 2006 04:31:25 -0500 X-Mail-Handler: MailHop Outbound by DynDNS X-Originating-IP: 87.49.211.44 X-Report-Abuse-To: abuse@dyndns.com (see http://www.mailhop.org/outbound/abuse.html for abuse reporting information) X-MHO-User: hogndos Message-ID: <4401756D.4080304@hogstrom.org> Date: Sun, 26 Feb 2006 10:31:25 +0100 From: Matt Hogstrom User-Agent: Mozilla Thunderbird 1.0.7 (Macintosh/20050923) X-Accept-Language: en-us, en MIME-Version: 1.0 To: dev@geronimo.apache.org Subject: Re: Changing Trunk to 1.2 in anticipation of 1.0.1 becoming 1.1 References: <43FA95C3.4010306@hogstrom.org> <43FAA09A.1020508@toolazydogs.com> <43FAAB3D.7070902@gmail.com> <43FE5793.7080009@hogstrom.org> <3F252A78-DEB9-4124-AD92-029B0F366B46@iq80.com> In-Reply-To: <3F252A78-DEB9-4124-AD92-029B0F366B46@iq80.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 Dain, Which part are you taking a crack at? I've done some of the HEAD work. Should I abandon that ? Matt Dain Sundstrom wrote: > Matt is traveling again, so I'm going to take a crack at this. > > -dain > > On Feb 23, 2006, at 4:47 PM, Matt Hogstrom wrote: > >> John, >> >> Life has been a travelling adventure lately so apologies for my tardy >> response. >> >> My thinking is as follows in order of steps: >> >> 1. Convert HEAD to 1.2 SNAPSHOT. This will be good as we need to get >> this story down to simply changing etc/project.properties or at least >> as close as possible. >> >> 2. Once HEAD is changed and building correctly hopefully Dain and >> David will have something to show. I know they've been bustin their >> chops working on this. We rename their branches/ configid to >> branches/1.1. We'd have to ensure that changes made to 1.0 since >> they started get moved into their branch and then we can delete the >> 1.0 branch since we have the 1.0.0.0 tag. >> >> 3. Apply the outstanding JIRA's I had previously identified. We need >> to figure out which ones are still important. >> >> I'd like to get the release out by the end of March. >> >> Is this clearer? >> >> Matt >> >> John Sisson wrote: >> >>> Alan D. Cabrera wrote: >>> >>>> On 2/20/2006 8:23 PM, Matt Hogstrom wrote: >>>> >>>>> I was thinking that in order to expedite getting 1.1 our the door >>>>> that it would make sense to move trunk to 1.2. Then we'll have to >>>>> do the same in the 1.0 branch. I'm going to start working on that >>>>> this week. Comments, suggestions, ? >>>> >>>> >>>> >>>> >>>> So what is in trunk now? What is in branches/1_0 now? Where is >>>> the work for 1_1 taking place? >>>> >>> Matt, >>> Could you please confirm the following.. >>> AFAIK, work for the 1.1 release (that was previously going to be >>> called the 1.0.1 release) should be done in the 1.0 branch (until we >>> branch for 1.1?). >>> Matt is proposing to change the version numbers in files in >>> branches/1.0 to be 1.1. I assume you plan on doing this before we >>> create the 1.1 branch? >>> Once the configId changes are merged in to branches/1.0 and we are >>> ready for a release we would create branches/1.1 from the 1.0 branch. >>> If we are creating a 1.1 branch then does that mean there would be >>> no further work happening in the 1.0 branch once the branch is made? >>> Work for the 1.2 release should be done in trunk. I think Matt is >>> proposing to change the version numbers in files in trunk to be 1.2. >>> Are we releasing version 1.1 of all the specs for the 1.1 release? >>> Thanks, >>> John >>> >>>> >>>> Regards, >>>> Alan >>>> >>>> >>>> >>>> > > > >