Page History

...

1. Grab the latest source from SVN

   Code Block
   svn co https://svn.apache.org/repos/asf/camel/trunk camel cd camel

2. Verify headers with rat

   Code Block
   mvn -e apache-rat:check grep -e ' !?????' target/rat.txt -- will show any files without licenses

3. Do a release dry run to check for problems

   Code Block
   mvn release:prepare -DdryRun=true

   Check that you are happy with the results. The poms for the proposed tags will be in pom.xml.tag. Check also the generated signature files:

   Code Block
   cmueller$ gpg camel-core/target/camel-core-2.7.5-SNAPSHOT.jar.asc gpg: Signature made Tue Jan 10 20:50:27 2012 CET using RSA key ID 2A239C2C gpg: Good signature from "Christian Mueller (CODE SIGNING KEY) <cmueller@apache.org>"

   When you like the results, clean up:

   Code Block
   mvn release:clean

4. Prepare the release

   Code Block
   mvn release:prepare

   This will create the tag in svn and leave various stuff around locally to direct the perform phase.
5. Perform the release to the staging repo

   Code Block
   mvn release:perform

6. Close the staging repository
   Quote from the Maven release guide for Apache projects

   Login to https://repository.apache.org using your Apache LDAP credentials. Click on "Staging". Then click on "camel" in the list of repositories. In the panel below you should see an open repository that is linked to your username and ip. Right click on this repository and select "Close". This will close the repository from future deployments and make it available for others to view. If you are staging multiple releases together, skip this step until you have staged everything. Enter the name and version of the artifact being released in the "Description" field and then click "Close". This will make it easier to identify it later.

   See the image in the original guide for more info.
7. Verify staged artifacts
   Quote from the original guide

   If you click on your repository, a tree view will appear below. You can then browse the contents to ensure the artifacts are as you expect them. Pay particular attention to the existence of *.asc (signature) files. If the you don't like the content of the repository, right click your repository and choose "Drop". You can then rollback your release and repeat the process.
   Note the repository URL, you will need this in your vote email.

...