Child pages
  • Releasing Qpid JMS AMQP 0-x
Skip to end of metadata
Go to start of metadata

This document summarizes the steps of release process for Qpid JMS AMQP 0-x


The release process is based on Apache Release PolicyRelease Signing and Publishing of Maven Documents


Release artifacts needs to be signed. GNU Privacy Guard from OpenPGP is used to sign on Apache. Please, refer Release Signing about PGP public key cryptography. The document provides basic information about release signing and contains links to various resources about PGP public key cryptography and how to use GNU Privacy Guard to generate and sign the PGP keys. Install GNU Privacy Guard, generate keys following steps provided here and upload public keys to keyservers . After publishing keys, login into and enter PGP key fingerprint(s), then the corresponding keys will be made available under within a few hours. Additionally, qpid project requires adding a public key into


Maven is used to build and manage Qpid Java project. 3.x version of maven needs to be installed and the development environment should be setup as described at Publishing of Maven Artifacts.

Please, note that repository id (server id) in setting xml should be apache.releases.https. Using different id would result in failures to publish release artifacts into staging maven repo.


Versions 6.4.0 and above

JDK 1.8 is required to compile java classes.

Versions below 6.4.0

JDK 1.7 is required to compile java classes. Install latest 1.7 JDK. At the moment of writing this document 1.7.0_80 JDK was the latest one.

Configure Java/Maven to use TLS 1.2

export JAVA_TOOL_OPTIONS="-Dhttps.protocols=TLSv1.2" 


Sources are kept in a Git repository. Thus a git client is required.

Major/Minor version release

  1. Checkout Qpid sources from trunk using git client.

    git clone qpid-jms-amqp-0-x
    cd ./qpid-jms-amqp-0-x
  2. Run RAT tool to verify that all source files have license headers

    mvn  apache-rat:check

    Check that images don't have a non-free ICC profile.

    find . -regextype posix-extended -iregex '.*\.(jpg|png|ico|tif)' -exec sh -c 'identify -verbose "$0" | grep -i copyright && echo "$0"' {} \;
  3. Check that build completes successfully using profile apache-release

    mvn clean install -Papache-release

    The gpg plugin will prompt for the password of PGP  signing key. If password is asked for every release artifact, then gpg2 should be configured to use. The easiest way to configure gpg2 is to add an active profile with pgp plugin settings into settings.xml:

        <!-- optional -->
  4. Add license headers to the files which do not have licenses. Update RAT excludes if required.

  5. Verify third party licenses

    mvn -Pdependency-check prepare-package -DskipTests

    The check should finish successfully. Otherwise, dependencies with not complaint licenses should be resolved before taking next release step.

    When new dependencies are added or changed the dependency verification files needs to be updated. In order to do so, run the command above with flag -Ddependency-change-verification=true

  6. Build alpha.

    1. Making an alpha build is optional and can be skipped if required. Alpha does not requires branching. The following chain of maven commands can be used to build and deploy alpha into staging repo
      Example of building 6.3.0-alpha

      mvn versions:set -DnewVersion=6.3.0-alpha ; mvn clean install deploy -Papache-release ; mvn versions:revert

      maven versions plugin is used to change version and revert it back after build and deploy

    2. On successful completion the build is deployed into staging repository, which needs to be closed in order to be available. Log into Apache Nexus UI, select the repository under "Staging Repository" and click Close button to close staging repository to prevent publishing of any new artifact. After closing, a permanent link to the staging repository will be available.
    3. Send an email into about alpha availability with a link to the staging repository.
    4.  Do not forget to delete staging repo after building RC or beta build. It requires logging into Apache Nexus UI, selecting the repository and clicking "Drop" button.
  7. Check JIRA system for any unresolved JIRAs for the release and notify assigned developers to take actions on uncompleted JIRAs
  8. Cut the branch using release:branch. Please, refer maven release plugin documentation for more details. For example, the following command was used to cut 6.3.x branch

    mvn release:branch -DbranchName=6.3.x -DupdateBranchVersions=false -DupdateWorkingCopyVersions=true  -DautoVersionSubmodules=true

    As part of execution command above maven asks about new version of the trunk sources and changes the version to provided one.

  9. Build beta if required following instructions in step 5 on branched sources
  10. Build RC

    1. Checkout branch sources, for example, 6.3.x branch is checked out as below

      git clone -b 6.3.x 6.3.x
      cd 6.3.x
    2. If it is not a first RC, remove previous tag from git

      git push --delete origin x.y.z

      where x.y.z is a tag version

    3. Cut the tag using maven:prepare

      mvn release:clean
      mvn release:prepare -Papache-release -DautoVersionSubmodules=true

      Release plugin will ask about new release version, tag name and new development version. Enter the same values for version and tag

      On successful execution a tag with a provided name will be created, the tag version will be set to the specified release version and development version on the branch will be changed to the provided one

    4. Build the RC and publish release artifacts into maven staging repo

      mvn release:perform -Papache-release

      release:perform will build release artifacts and deploy them into staging repo. Note that this will do a clean checkout so it might take a while.

    5. The staging maven repository needs to be closed. Log into Apache Nexus UI, select the repository under "Staging Repository" and click Close button to close staging repository for any publishing of artifacts. After closing, a permanent link to the staging repository will be available.
    6. Copy source and binary bundles and their signatures/checksum files from the nexus staging repository into qpid dev staging area at under the sub-folder with the same name as tag. Binary bundles  and their signatures/checksum files need to be put into sub-folder with name binaries. (Not doing so would break the site).

      Use curl or wget to download all broker and client tar.gz and zip bundles and their signatures from maven staging repo like so:

      mkdir binaries
      for i in "" ".asc"; do
          curl -O  $root/org/apache/qpid/apache-qpid-jms-amqp-0-x/$version/apache-qpid-jms-amqp-0-x-$version-src.tar.gz$i
          if [[ "$i" == "" ]]; then
              sha512sum apache-qpid-jms-amqp-0-x-$version-src.tar.gz > apache-qpid-jms-amqp-0-x-$version-src.tar.gz.sha512
      cd binaries
      for i in "" ".asc"; do
          for j in "tar.gz" "zip"; do
              curl -O  $root/org/apache/qpid/apache-qpid-jms-amqp-0-x/$version/apache-qpid-jms-amqp-0-x-$version-bin.$j$i
      for j in "zip" "tar.gz"; do
        sha512sum apache-qpid-jms-amqp-0-x-$version-bin.$j > apache-qpid-jms-amqp-0-x-$version-bin.$j.sha512
      for j in "zip" "tar.gz"; do
         sha512sum -c apache-qpid-jms-amqp-0-x-$version-bin.$j.sha512
         gpg --verify apache-qpid-jms-amqp-0-x-$version-bin.$j.asc
      cd ..
      sha512sum -c apache-qpid-jms-amqp-0-x-$version-src.tar.gz.sha512
      gpg --verify apache-qpid-jms-amqp-0-x-$version-src.tar.gz.asc
    7. Send an email into about RC availability with links to the maven staging repository and qpid dev staging area folder containing source and binary bundles

  11. If RC is OK and voting passes, publish release artifacts:
    1. send a email to to close the vote. This should include the number of binding and non-binding votes, the result, and a link to the voting thread (use Apache services (this or
    2. promote maven staging artifacts from staging repository into the world by pressing Release button in Apache Nexus UI.
    3. copy source and binary bundles and their signatures/checksum files form dev staging are into release distribution area. For example, the commands below copy dev 6.3.1 artifacts into final 6.3.1

      svn cp -m "QPID-8190: Publish release artifacts for JMS AMQP 0-x 6.3.1"

      If voting does not pass, resolve found issues, drop staging repository, delete svn tag and repeat instructions from step 9 until voting passes.

  12. Wait for 24 hours after closing the vote
  13. Update Qpid web site Qpid JMS AMQP 0-x pages and publish new release documentation following instructions here.
    Java 8 could be required for latest fop/docbook dependencies. Here are sample commands which could be used to create 6.3.1 release pages on the website based on the 6.3.1 tag.

    git clone site
    cd ./site
    make gen-jms-amqp-0-x-release RELEASE=6.3.1 ISSUES_RELEASE=qpid-java-client-0-x-6.3.1
    vim ./input/releases/qpid-jms-amqp-0-x-6.3.1/ # headline major enhancements and new features
    vim ./input/              # Update the current release pointer
    vim ./input/releases/               # Add current release, move the previous
    make render
    make check-links
    make publish
    git add input/
    git add content/
    git commit -m "Update site for Qpid JMS AMQP 0-x release 6.3.1"
    git push

  14. Mark release as released in JIRA and close any unresolved JIRAs if required
  15. Send the release notification email into and

    Note, In order to send messages into one need to send the mail with the From field set to one's address. Gmail can be set-up to do so via use of the ASF mail relay. The details how to set up apache account to use ASF mail relay can be found in the following resources

  16. Remove the previous release binaries from when a new one is announced
  17. Create jenkins jobs for new major/minor version

Bugfix release procedure

Execute steps 1-7 and 9-16 from Major release procedure on branch sources.

  • No labels