Re: Release preparation
Karl Pauls wrote: putting our releases up to the maven repository was a little bit work, as I had to create the correct directory structure by hand and (more important) had to extract the pom files for the various artifacts, create md5s and sign them. On this subject, would you mind if I replace your signature with our release key signature? I think that would make it more consistent since that is the key we currently use for the artifacts. I don't mind - go ahead - alternatively I could add my key to the keys file. Whatever you prefer. Carsten -- Carsten Ziegeler [EMAIL PROTECTED]
Re: Release preparation
The release plugin now supports a staging area. One can take a look at CXF for example (or maybe the naven site). Interesting. I'll definitely have a look at that! regards, Karl On 7/21/07, Niclas Hedhman [EMAIL PROTECTED] wrote: On Saturday 21 July 2007 01:34, Carsten Ziegeler wrote: We could also use the maven release plugin to do all the work for us. Together with the gpg plugin it creates all necessary artifacts, signs them etc. Yes, releasing large number of Maven artifacts without the help of the release plugin is pain in many unspoken places... However, AFAIK, the release plugin does not support a staging, release candidate or similar repo, so that one can publish to the non-official final destination, for review and votes. And we can't upload until after the vote. But I would be interested to learn how to leverage the release plugin. Below is an explanation of what I would have in mind. 1. Each maven artifact extends a parent named org.apache.felix:candidate. 2. That parent defines all the upload locations to some staging area on people.apache.org, and tagging the sources into a similar area in SVN. 3. One executes a mvn release:prepare/perform on TRUNK, and things is made available for review. 4. The vote is executed. 5. If it passes, one modifies the candidate branch in SVN and replaces the candidate parent to a org.apache.felix:final pom. 6. That pom has the tagging and uploading set to the final resting place in both SVN, artifacts uploads, tar ball uploads and documentation (if any). WDYT? In fact, this is of strong interest to the entire ASF, and I would like to hear from Carlos how Maven itself does it, since they have this problem at a grand scale. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug -- Cheers, Guillaume Nodet Principal Engineer, IONA Blog: http://gnodet.blogspot.com/ -- Karl Pauls [EMAIL PROTECTED]
Re: Release preparation
I'd like to but i'o in holidays too. I may be able to help in a few weeks. On 7/20/07, Marcel Offermans [EMAIL PROTECTED] wrote: On Jul 20, 2007, at 19:34 , Carsten Ziegeler wrote: We could also use the maven release plugin to do all the work for us. I agree, automating the whole release process is something that should be on our list for the next release. Karl has just gone on holiday for a couple of weeks, but perhaps you can have a look at the changes we need to make and come up with a patch? Greetings, Marcel -- Cheers, Guillaume Nodet Principal Engineer, IONA Blog: http://gnodet.blogspot.com/
Re: Release preparation
On Saturday 21 July 2007 01:34, Carsten Ziegeler wrote: We could also use the maven release plugin to do all the work for us. Together with the gpg plugin it creates all necessary artifacts, signs them etc. Yes, releasing large number of Maven artifacts without the help of the release plugin is pain in many unspoken places... However, AFAIK, the release plugin does not support a staging, release candidate or similar repo, so that one can publish to the non-official final destination, for review and votes. And we can't upload until after the vote. But I would be interested to learn how to leverage the release plugin. Below is an explanation of what I would have in mind. 1. Each maven artifact extends a parent named org.apache.felix:candidate. 2. That parent defines all the upload locations to some staging area on people.apache.org, and tagging the sources into a similar area in SVN. 3. One executes a mvn release:prepare/perform on TRUNK, and things is made available for review. 4. The vote is executed. 5. If it passes, one modifies the candidate branch in SVN and replaces the candidate parent to a org.apache.felix:final pom. 6. That pom has the tagging and uploading set to the final resting place in both SVN, artifacts uploads, tar ball uploads and documentation (if any). WDYT? In fact, this is of strong interest to the entire ASF, and I would like to hear from Carlos how Maven itself does it, since they have this problem at a grand scale. Cheers -- Niclas Hedhman, Software Developer I live here; http://tinyurl.com/2qq9er I work here; http://tinyurl.com/2ymelc I relax here; http://tinyurl.com/2cgsug
