Page History

...

Basically, setup your settings.xml file as they described except for your gpg key. The version of the gpg plugin we use will ask for it. The deploy.altRepository should be set to something similar to:

...

...

apache.releases::default::scp://people.apache.org/home/dkulp/public_html/maven_staging

After that is setup, you need to update the release_notes.txt in the distribution/src/main/release, and run the below commands.

...

That will tag the release, update the poms, etc... Then build it (off the tag) and deploy everything (including source jars and javadoc jars) to the deploy.altRepository Nexus repository location and gpg signs everything. Once there, call the vote(s) based on that. When the build is done staging, you need to login to the Nexus repository and "close" the staging are. See the Maven page above for instructions. That is very important. After the staging are is closed, note the URL for the staging area as you will need that for the vote.

At this point, everything "pre-vote" is done. Call the vote.

After the vote passes, you'll need to "merge" promote that staging location repository to the main location. The maven "stage" plugin is used to do this. Just run:

mvn stage:copy \
   -Dsource="http://people.apache.org/~dkulp/stage_cxf/2.1/maven" \
   -Dtarget="scp://people.apache.org/www/people.apache.org/repo/m2-ibiblio-rsync-repository" \
   -Dversion=2.1
   -DtargetRepositoryId=apache.releases

One note: according to the Maven folks, the stage:copy stuff apparently doesn't work on Windows. Don't bother trying. Use Linux or OSX.

One other note: The current version (as of 10 December 2008) of the stage plugin explodes
on contact with Maven 2.0.9. Use 2.0.8 until further noticeLogin to Nexus to do that as well. See above Maven team release page.

Also, don't forget to copy the actual distributions to people.apache.org:/www/www.apache.org/dist/cxf.

...