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.225 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=WlaM1Lt7KU96fPT8k+KNqcQt0vHqIkr66/paw/UFs45GPKMYj08nh5Qt1Ldq/Ge1NFV6MvF6mqAS27aPIqT0gRK6ZnJ+ABnyDtLraj7jzon+xLAeUr2/GzP5a19+5E2Mb6AivD1r8/hGt9ef1hv9IY+m9F5b4pc3THogHwLFYNM=
Mime-Version: 1.0 (Apple Message framework v750)
In-Reply-To: <4499E96C.7040408@hogstrom.org>
References: <4499D2EE.7050905@hogstrom.org>
 <11AED463-EBCD-42CE-87F6-481F51281CD6@planet57.com>
 <af2843cd0606211654n51c3d916n446d0c11fa1fe5c5@mail.gmail.com>
 <8F213124-C3EC-4626-9D48-A9EC0BD03ADA@planet57.com>
 <4499E96C.7040408@hogstrom.org>
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
Message-Id: <5F0DEB97-D228-4673-ADE0-7BE575745750@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:20:07 -0700
To: dev@geronimo.apache.org
From: Jason Dillon <jason@planet57.com>
Sender: Jason Dillon <jason.dillon@gmail.com>

> I think your right if nothing needs to change.  IIUC there is a  
> general preference for tags being pristine with no modifications.

Generally I agree with this.


> So, if a release can go from being worked to a good release then  
> the Maven system is great.  I think the reality is that there will  
> generally be the time required to wait for a release to bake.  If  
> changes are needed then they either need to be applied to the  
> tagged version or copied and re-tagged (which IMHO is really  
> undesireable).

What kind of release backing are we talking about?


> I think the idea of no changes to tags makes sense.  If Maven could  
> handle the process and take into account the timing and possible re- 
> work that would be awesome.  Right now the 1.1.0 release has been  
> there for the better part of two weeks.  I don't think we want to  
> stall development like this in the future.

Agreed.  Maven should be able to help... m2 that is, not sure about  
m1.  I'm going to experiment with a GShell release, but from what I  
understand, the release plugin should automate most of the details.

We'll see.

--jason