Page History

...

1. grab the latest Source

   Code Block
   svn co https://svn.apache.org/repos/asf/servicemix/$PART/trunk

   where $PART is what you want to release. For example, it can be:
   • smx3
   • smx4
   • components/bindings/servicemix-cxf-bc
   • ...
2. prepare your POMs for release:
   1. make sure there is no snapshots in the POMs to be released
   2. make sure everything builds fine
   3. check that your POMs will not lose content when they are rewritten during the release process:

      Code Block
      mvn release:prepare -DdryRun

      and diff the original pom.xml with the one named pom.xml.tag to see if the license or any other info has been removed. This has been known to happen if the starting <project> tag is not a single line. The only things that should be different between these files are the <version> and <scm> elements. If there are any other changes, you must fix the original pom.xml file and commit before proceeding with the release.
   4. publish a snapshot

      Code Block
      $ mvn deploy ... [INFO] [deploy:deploy] [INFO] Retrieving previous build number from apache.snapshots.https ...

   • if you experience an error during deployment like a HTTP 401 check your settings for the required server entries as outlined in the Prerequisites
   • be sure that the generated artifacts respect the Apache release rules: NOTICE and LICENSE files should be present in the META-INF directory within the jar. For sources artifacts, be sure that your POM does not use the maven-source-plugin:2.0.3 which is broken. The recommended version at this time is 2.0.4
   • you should verify the deployment under the snapshot repository on Apache
3. prepare the release

   Code Block
   mvn release:clean mvn release:prepare

4. stage the release for a vote
   Note: If you're on Mac OSX 10.5, for a known issue, you need provide your apache svn user/password
   mvn release:prepare -Dusername=ffang -Dpassword=*******

   Code Block
   mvn release:perform

   • the release will automatically be inserted into a temporary staging repository for you, see the Nexus staging documentation for full details
   • you can continue to use mvn release:prepare and mvn release:perform on other sub-projects as necessary on the same machine and they will be combined in the same staging repository
5. close the staging repository
   • login to https://repository.apache.org using your Apache SVN credentials. Click on Staging on the left. Then click on org.apache.servicemix 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
     
6. verify the staged artifacts
   • 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 you don't like the content of the repository, right click your repository and choose Drop. You can then rollback your release (see Canceling the Release) and repeat the process
   • note the staging repository URL (especially the number at the end of the URL) you will need this in your vote email

...

To: "ServiceMix Developers List" <dev@servicemix.apache.org>
Subject: [RESULT] [VOTE] Release ServiceMix [Component] XXX version Y.Z

Hi,

The vote has passed with the following result :

  +1 (binding): <<list of names>>
  +1 (non binding): <<list of names>>

I will copy this release to the FelixServiceMix dist directory and
promote the artifacts to the central Maven repository.

...

1. remove the release tag from Subversion (svn del ...)
2. login to https://repository.apache.org^{Image Removed} using your Apache SVN credentials. Click on Staging on the left. Then click on org.apache.servicemix in the list of repositories. In the panel below you should see a closed repository that is linked to your username and IP (if it's not yet closed you need to right click and select Close). Right click on this repository and select Drop.
3. rollback the version in the pom.xml and commit any fixes you need to make

...

1. copy the released artifacts to the ServiceMix dist directory (/x1/www/www.apache.org/dist/servicemix) on people.apache.org
2. delete the old release from the ServiceMix dist directory (it's archived)
3. login to https://repository.apache.org^{Image Removed} with your Apache SVN credentials. Click on Staging. Find your closed staging repository, right click on it and choose Promote. Select the Releases repository from the drop-down list and click Promote.
4. next click on Repositories, select the Releases repository and validate that your artifacts are all there
5. update the news section on the website at news
6. update the download page on the website at downloads to point to the new release.

...