release-notes

Make sure you have gpg keys
1. gpg --list-keys
2. gpg --list-secret-keys

Test that you can sign a file
1. gpg -ab testfile

Make sure that ~/.m2/settings.xml contains the following profile:

    <profile>
      <id>release-sign-artifacts</id>
      <activation>
        <property>
          <name>performRelease</name>
          <value>true</value>
        </property>
      </activation>
      <properties>
        <gpg.passphrase>PASSPHRASE</gpg.passphrase>
        <gpg.useagent>true</gpg.useagent>
        <gpg.defaultKeyring>false</gpg.defaultKeyring>
      </properties>
    </profile>
  </profiles>

New version of gpg will fail to sign artifacts, to workaround this check https://issues.apache.org/jira/browse/MGPG-59
and run:

gpg --use-agent --armor --detach-sign --output $(mktemp) pom.xml

This command will bring up the window to put your passphrase and will create a temp file to be used during the release process.

mvn release:prepare -Pmaven-release --batch-mode -DdevelopmentVersion=2.0.4-SNAPSHOT -DreleaseVersion=2.0.3 -Dtag=2.0.3 -Darguments="-Dmaven.test.skip=true"

Notice there is a maven-release plugin bug that the created branch for release has -SNAPSHOT in the version, check herehttps://stackoverflow.com/questions/16650698/maven-release-plugin-prepare-creates-tag-of-snapshot-version-instead-of-releas
Patch has been provided in the pom.xml according to the link

mvn release:perform -Pmaven-release,release-sign-artifacts -Darguments="-Dmaven.test.skip=true"


Next login in https://oss.sonatype.org/index.html, click staging repositories, then click close button.
After repository is closed, click release button.