You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 4 Next »

This document summarizes the steps of release procedure for Qpid Java Components
The Qpid release process is based on Publishing of Maven Documents
The purspose of this document is to describe the release procedure for Qpid Java Components.

Pre-Requirements

The release manager should be familiar with Apache Release Policy,  Release Signing and Publishing of Maven Documents

PGP

Install GNU Privacy Guard from OpenPGP and have generated and signed PGP keys. Please, refer Release Signing about PGP public key cryptography. The document contains basic information about release signing and contains link to various resources about PGP public key cryptography and how to use GNU Privacy Guard to generate and sign the PGP keys.


Briefly,

  1. install GNU Privacy Guard
    for Red Hat based systems (Fedora, Centos OS, Red Hat Enterprise Linux) simply use yum to install gpg:

    sudo yum install gnupg
  2. generate your master key and sub-key following steps provided here
  3. sign the keys

Maven

The Qpid Java Components requires 3.x version of Maven. Add your credentials for Apache maven repository into maven settings.xml as required in Publishing of Maven Documents.

 

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.

Java

JDK 1.7 is required

SVN


Latest SVN client should be installed

Major release procedure

  1. Checkout Qpid sources from trunk using svn client. Alternatively, git and git-svn can be used.

    svn co https://svn.apache.org/repos/asf/qpid/java/trunk qpid-java
cd ./qpid-java

  2. Check that you can build using profile apache-release

    mvn clean install -Papache-release -DskipTests -Dmaven.javadoc.skip=true

    The build should finish successfully. The gpg plugin will prompt for the key for signing of the build artifacts.

  3. Run RAT tool to verify that all source files have license headers

    mvn  apache-rat:check

    Add license headers to the files which do not have one or update RAT excludes if required.

  4. Verify third party licenses

    mvn -Pdependency-check prepare-package

  5. Build alpha
    Alpha does not requires branching. Thus, it can be built using maven versions plugin to change version and revert it back after build and deploy, for example

    mvn versions:set -DnewVersion=6.0.0-alpha ; mvn clean install deploy -Papache-release ; mvn versions:revert
  6. The build is deployed into staging repository, which needs to be closed in order to be available. Log in 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.
  7. Send an email into users@qpid.apache.org about alpha availability with a link to the staging repository
  8. When beta is ready to be created and published, delete the staging repository by logging into Apache Nexus UI, selecting the repository and clicking "Drop" button.
  9. Check JIRA system for any unresolved JIRAs for the release and notify authors about the release

  10. Cut the branch using release:branch. Please, refer maven release plugin documentation for more details

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

  11. Checkout branch sources, for example

    svn co https://svn.apache.org/repos/asf/qpid/java/branches/6.0.x
cd 6.0.x

  12. Cut the tag and build the release build using maven:prepare

    mvn release:clean
mvn release:prepare -Papache-release,qpid-bdb.0-9

    Preparing the release will create the new tag in SVN, automatically checking in on your behalf.
  13. Stage the release for voting
    mvn release:perform -Papache-release,qpid-bdb.0-9
  14. The build is deployed into staging repository, which needs to be closed in order to be accessible. 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.
  15. Send an email into users@qpid.apache.org about RC availability with a link to the staging repository
  16. If RC is OK and voting passes, promote the artifacts from staging repository into the world by pressing Release button in Apache Nexus UI.
    Otherwise, drop staging repository and repeat steps 12-16 until voting passes.
  17. Update Qpid web site Qpid Java Component pages and publish new release documentation.

    The website readme has more detail about these steps.


       - Generate new release content

       - Add any additional notes desired to the generated release notes

       - Change current release version

       - Update release references in other parts of the site
  18. Mark release as released in JIRA and close any unresolved JIRAs if required
  19. Wait for 24 hours after closing the voting and send the release notification email into users@qpid.apache.org

Minor release procedure

Follow the steps 11-19 from Major release procedure. If required, it can include steps 3-9 for running RAT, verifying licenses and building alpha (with difference of checking out sources from svn branch).

  • No labels