Building a release for vote:

  1. Grab a clean checkout for safety.
  2. Run: “git checkout ${BRANCH}” to switch to a branch of the intended release point.
  3. Run: “bin/ ${VERSION} ${TAG}”, e.g. bin/ 0.10 0.10-rc1.
  • This will create a detached-HEAD state, manipulate the versions, and then create the tag.
  1. Run: “git push origin ${TAG}” as directed by the script.
  • This can be deferred until later if desired, following archive creation and testing etc.
  1. Run: “bin/ $PWD ${TAG}” to create the qpid-proton-${TAG}.tar.gz release archive.
  2. Create signature and checksums for the archive:
  • e.g “gpg --detach-sign --armor qpid-proton-${TAG}.tar.gz”
  • e.g “sha1sum qpid-proton-${TAG}.tar.gz > qpid-proton-${TAG}.tar.gz.sha”
  • e.g “md5sum qpid-proton-${TAG}.tar.gz > qpid-proton-${TAG}.tar.gz.md5”
  1. Deploy the Java binaries to a staging repo:
  • Run: “tar -xzf qpid-proton-${TAG}.tar.gz”
  • Run: “cd qpid-proton-${VERSION}”
  • Run: “mvn deploy -Papache-release -DskipTests=true”
  1. Close the staging repo:
  • Log in at
  • Find the new ‘open’ staging repo just created and select its checkbox.
  • Click the ‘close’ button, provide a description, e.g “Proton ${TAG}” and close the repo.
  • Wait a few seconds, hit the ‘refresh’ button and confirm the repo is now ‘closed’.
  • Click on the repo and find its URL listed in the summary.
  1. Commit artifacts to dist dev repo in${TAG} dir.
  2. Send email, provide links to dist dev repo and the staging repo.

After a vote succeeds:

  1. Bump the master/branch version to next 0.x-SNAPSHOT if it wasnt already.
  2. Tag the RC with the final name/version.
  3. Commit the artifacts to dist release repo in${RELEASE} dir:
  • Rename the files to remove the RC suffix.
  • Fix filename within .sha and .md5 checksums or regenerate.
  1. Update the ‘latest’ link in
  2. Release the staging repo:
  1. Give the mirrors some time to distribute things.
  2. Update the website with release content.
  3. Update development roadmap.
  4. Send release announcement email.