Fork me on GitHub

Release Process

There are two distinct sets of artifacts in two repositories that are typically released together: apache-streams and apache-streams-examples.

apache-streams artifacts include streams source code and convenience jars by module.

apache-streams-examples source code builds ready-to-run stand-alone examples as uber-jars.

Releases must be built and published in the following order:

  • apache-streams
  • apache-streams-examples

In the instructions below, ${} should be one of these top-level repository aggregator pom project names.


As a streams release manager, you probably want to use the and scripts in the root of apache-streams.

To perform a release manually, or to better understand what’s going on, read the instructions below.

In either case, you’ll need to first refer to Release Setup Information.

Common Release Steps

  1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)

    1. Use the latest Sun 1.8.x JDK
    2. Use Maven 3.3.9 or later
    3. Make sure the Release Setup steps have been performed.
  2. Prepare the source for release:

    1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly.
    2. Update the text files in a working copy of the project root -
      1. Update the CHANGELOG based on the Text release reports from JIRA.
      2. Review and update if needed.
      3. Commit any changes back to git
    3. Stage any Roadmap or Release landing pages on the site.
  3. Create a release candidate branch from master.

X should start at 1 and increment if early release candidates fail to complete the release cycle.

    git checkout master
    git branch ${}-${project.version}-rcX
    git checkout ${}-${project.version}-rcX
  1. Verify the source has the required license headers before trying to release:

    mvn -Papache-release clean apache-rat:check -e -DskipTests
  2. Do a dry run of the release:prepare step:

    mvn -Papache-release release:prepare -DautoVersionSubmodules=true -DdryRun=true
    • The dry run will not commit any changes back to SCM and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :
    * Release version - take the default (should be ${project.version})
    * SCM release tag - *DO NOT TAKE THE DEFAULT*  - ${project.artifactId}-${project.version}-rcX
    * New development version - take the default (should be ${project.version}-SNAPSHOT)
    * GPG Passphrase  
    • If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean goal to just remove the extra files that were created.
    • The Maven release plugin checks for SNAPSHOT dependencies in pom’s. It will not complete the prepare goal until all SNAPSHOT dependencies are resolved.
  3. Verify that the release process completed as expected

    1. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it’s corresponding pom.xml file should be the version number.
    2. Check and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
    3. Verify signatures (Verifying release signatures)
  4. Cleanup the release prepare files again:

    mvn -Papache-release release:clean
  5. Prepare the release

    1. Run the “release:prepare” step for real this time. You’ll be prompted for the same version information.
        mvn -Papache-release -U clean release:prepare -DautoVersionSubmodules=true
    1. Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.
  6. Perform the release

    • This step will create a maven staging repository and site for use in testing and voting.
        mvn -Papache-release -Darguments='-Dmaven.test.skip.exec=true' release:perform -Dgoals=deploy -DlocalRepoDirectory=. -DlocalCheckout=true
    • If your local OS userid doesn’t match your Apache userid, then you’ll have to also override the value provided by the OS to Maven for the site-deploy step to work. This is known to work for Linux, but not for Mac and unknown for Windows.*[your_apache_uid]
  7. Verify the Nexus release artifacts

    1. Verify the staged artifacts in the nexus repo
    1. Close the nexus staging repo
      • Staging repositories (under Build Promotion) –> Name column –> org.apache.streams
      • Click checkbox for the open staging repo (org.apache.streams-XXX) and press Close in the menu bar.
  8. Put the release candidate up for a vote

    1. Create a VOTE email thread on dev@ to record votes as replies
    2. Create a DISCUSS email thread on dev@ for any vote questions
    3. Perform a review of the release and cast your vote. See the following for more details on Apache releases
    4. A -1 vote does not necessarily mean that the vote must be redone, however it is usually a good idea to rollback the release if a -1 vote is received. See - Recovering from a vetoed release
    5. After the vote has been open for at least 72 hours, has at least three +1 PMC votes and no -1 votes, then post the results to the vote thread by -
      • reply to the initial email and prepend to the original subject “[RESULT]”
      • Include a list of everyone who voted +1, 0 or -1.
    6. Promote the staged nexus artifacts
      • Staging repositories (under Build Promotion) –> Name column –> org.apache.streams
      • Click checkbox of the closed staging repo (org.apache.streams-XXX) and select Release.
  9. Complete the release

    1. Copy the source artifacts over to the distribution area
        svn co ./streams-releases  (KEEP this directory until after the release process has been completed)
        cd ./streams-releases
        mkdir ${project.version}
        cd ./${project.version}
        svn add ${}-*
        svn commit -m "Committing Source Release for ${}-${project.version}
    1. Create an official release tag from the successful release candidate tag.
        git checkout ${}-${project.version}-rcX
        git tag -a ${}-${project.version} -m 'release tag ${}-${project.version}'
        git push origin :refs/tags/streams-project-${project.version}
    1. Update the staged website
      • Update the downloads page ( to add new version using the mirrored URLs
      • Modify the URL for the prior release to the archived URL for the release
    1. Publish the website (see website)
      • WAIT 24hrs after committing releases for mirrors to replicate
      • Publish updates to the download page
    1. Delete the prior versions
      • Navigate to the release directories checked out in the prior steps
      • Delete the prior release artifacts using the svn delete command
      • Commit the deletion
  10. Update the JIRA versions page to close all issues, mark the version as “released”, and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.

  11. Announcing the release

Recovering from a vetoed release

  1. Reply to the initial vote email and prepend to the original subject -


  2. Clean the release prepare files and hard reset the release candidate branch.

    mvn -P apache-release release:clean
  3. Delete the git tag created by the release:perform step -

    git tag -d streams-project-${project.version}-rcX
    git push origin :refs/tags/streams-project-${project.version}-rcX
  4. Delete the build artifacts on people & www

    rm -rfv /www/${project.version}
    rm -rfv /www/${project.version}
  5. Drop the nexus staging repo

    2. Enterprise –> Staging
    3. Staging tab –> Name column –> org.apache.streams
    4. Right click on the closed staging repo (org.apache.streams-XXX) and select Drop.
  6. Remove the staged site

  7. Make the required updates that caused the vote to be canceled during the next release cycle

Verifying release signatures

On unix platforms the following command can be executed -

for file in `find . -type f -iname '*.asc'`
    gpg --verify ${file}

You’ll need to look at the output to ensure it contains only good signatures -

gpg: Good signature from … gpg: Signature made …

Combined Release

In order to perform a combined release of the streams-master and streams-project trunks, do the following:

  • Perform Steps 1-9 of the release for apache-streams and apache-streams-examples

    • Do NOT perform step 10 until steps 1-9 have been completed for BOTH projects
    • Build the streams-master FIRST
    • When prompted to change dependencies on SNAPSHOTs, do so to the corresponding releases that you just built
  • Execute the remaining steps using the following e-mail template

      subject: [VOTE] Apache Streams ${release.version} Release Candidate
      I've created a combined ${release.version} release candidate, with the
      following artifacts up for a vote:
      apache-streams source tag (r${release.version}):;a=commit;h=...
      apache-streams-examples source tag (r${release.version}):;a=commit;h=...
      Maven staging repo:${release.project.repository}${release.examples.repository}
      Source releases:${release.project.repository}/org/apache/rave/rave-project/${release.version}/streams-project-${release.version}${release.project.repository}/org/apache/rave/rave-project/${release.version}/streams-project-${release.version}
      Checksums of streams-project-${release.version}
      Checksums of streams-examples-${release.version}
      Release artifacts are signed with the following key:
      Please take the time to verify the artifacts before casting your vote.
      Vote will be open for 72 hours.
      [ ] +1  approve
      [ ] +0  no opinion
      [ ] -1  disapprove (and reason why)
Licensed under Apache License 2.0 -