Done. The branch is:
https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.10-RC
-j
Brian E. Fox wrote:
Sure, we can do that.
-----Original Message-----
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 10, 2008 1:55 PM
To: Maven Developers List
Subject: Re: Preparing for 2.0.10 RC1
I was thinking the same thing the other day. I think this is a good
idea.
-john
Arnaud HERITIER wrote:
In the process couldn't we create a 2.0.10-RC branch where we fix
issues
discovered in RCs.
At the end we create the final release from this branch and we merge
changes
in the 2.0.x trunk.
We that we are sure that no other commit on 2.0.x can be added by
error in
the RC process.
(it's just a proposal if we want to secure this process, because I
think it
never happened)
Arnaud
On Thu, Jul 10, 2008 at 6:01 PM, Brian E. Fox
<[EMAIL PROTECTED]>
wrote:
1) we will stop to fix any regressions between 2.0.9 and
2.0.10
What's the rationale for this?
I meant stop the current RC to fix the issue and then recut the next
RC. We
won't respin for other random issues.
--
John Casey
Developer, PMC Member - Apache Maven (http://maven.apache.org)
Blog: http://www.ejlife.net/blogs/buildchimp/
