Rahul Akolkar wrote:
On 9/16/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
Hi all
I'd like to prepare the release of commons-logging 1.1.1. The release
will be done entirely with Maven 2. Since this is fairly new for
Commons, I'd like to hear you opinions on how this should be done.
<snip/>
I don't think using m2 changes the crux of our release process, and
what you articulate below seems in line with what we do now.
That was what I was hoping for.
Couple of comments below:
Previous discussions regarding our release process indicate that voting
on a release should be done on the "actual bits". This can be difficult
do achieve, depending on what the process looks like.
Here's how we do it over at the Maven project. See [1] for full details.
1. Create a tag in svn with the actual release number (not an rc)
<snap/>
Indeed.
2. Build the entire distribution from the tag
3. Upload the distributions to people.a.o/~username for review/vote
4.1 If the vote is positive, move the distribution to the central m2
repository
<snip/>
So there was a tool that purportedly helped merged repository metadata
while moving. Is it at all of any significance to try to merge the
metadata?
Yes, there is a plugin that does this, maven-stage-plugin. We have been
using it internally at Maven for a couple months, refining it and fixing
bugs that come up. It's not released yet, but has reached a point where
I consider it ready for a first release.
-Rahul
4.2 If the vote is negative, remove the tag from svn and start again
Most of this is fully automated and supported by Maven 2 and plugins.
Does this sound like a good way to do releases using Maven 2 here in
Commons, as well?
[1] http://maven.apache.org/developers/release/releasing.html
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
