Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of jason.dillon@gmail.com
 designates 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:mime-version:in-reply-to:references:content-type:message-id:content-transfer-encoding:subject:date:to:x-mailer:from:sender;
        b=QGpQ1XwST0SAQOSASUt0CWM+Dq2iGANMcbqpGqs2CCgFgmPD9EbXKm3ux28TDxg182f9CTSYYxMg7tN5LcTwTwLl1HmHQ5jaeI4NrCrPuTzT1LvidE0UZiWmoP3zxqxmjHZRFVerdhMokodvEAppvZ+pva1NJ0l6+FEpTYbNL4c=
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <af2843cd0606211754i7439f3b0w43fc4f9a9d479428@mail.gmail.com>
References: <4499D2EE.7050905@hogstrom.org>
 <11AED463-EBCD-42CE-87F6-481F51281CD6@planet57.com>
 <af2843cd0606211654n51c3d916n446d0c11fa1fe5c5@mail.gmail.com>
 <8F213124-C3EC-4626-9D48-A9EC0BD03ADA@planet57.com>
 <af2843cd0606211754i7439f3b0w43fc4f9a9d479428@mail.gmail.com>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <36B3D160-0636-4F23-B12D-051837C1D2D9@planet57.com>
Content-Transfer-Encoding: 7bit
Subject: Re: Life After 1.1 - starting the new branch for 1.1.1 - some
 logistics and your input requested.
Date: Wed, 21 Jun 2006 18:12:50 -0700
To: dev@geronimo.apache.org
From: Jason Dillon <jason@planet57.com>
Sender: Jason Dillon <jason.dillon@gmail.com>

> Hi Jason,

Hiya :-)


> The problem is that it can take weeks to do a geronimo release since
> stuff like CTS testing is involved.  So the release work (putting the
> finishing touches) needs to be done in a branch so that work can
> continue on the next release.

I would hope that most if not all of the issues should be resolved  
wrt/CTS/TCK before making a release...

But, if this branch exists only for the reason of facilitating this  
time consuming process, and no merging is to be done, then I think it  
will work.

I think that all development should be done on the 1.1 (or trunk) or  
M.m branch, and only release work on any M.m.r branches, and at the  
end of the release that branch is moved to a tag and never modified  
again.  Future modifications will copy from the tag to a branch, and  
the cycle continues.


> Perhaps m2 has a way of dealing with those issues along with
> re-cutting releases and such.  But since I have not done a m2 based
> release yet, I'm not sure what's involved.  Could you clarify it a bit
> for me?

I'm actually still sorting that out.  I'm going to use m2 for GShell  
releases and I want to get a 0.0.1 out soonish to test it all out.   
I've got a little experence with it, and it does make it much easier,  
since for m2 every pom.xml needs to change when a version is changed :-(

--jason