Make the Release

1. This step will create a maven staging repository and site for use in testing and voting.

   `mvn release:perform -Papache-release`.
   Note: 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: -Duser.name=[your_apache_uid] --This is known to work for Linux, but not for Mac and unknown for Windows--.
   

Verify the Nexus release artifacts

• Verify the HTML links on site are correct

• Verify the staged artifacts in the nexus repo

  • https://repository.apache.org/index.html
  • Staging repositories (under Build Promotion) --> Name column --> org.apache.airavata
  • Navigate through the artifact tree and make sure that all Javadoc, sources, tests, jars, ... have .asc (GPG signature) and .md5 files. See http://people.apache.org/~henkp/repo/faq.html and http://www.apache.org/dev/release-signing.html#openpgp-ascii-detach-sig

• Close the nexus staging repo

  • https://repository.apache.org/index.html
  • Staging repositories (under Build Promotion) --> Name column --> org.apache.airavata
  • Click the checkbox for the open staging repo (org.apache.airavata-XXX) and press Close in the menu bar.

Sign the binary artifacts

* $ `cd modules/distribution/target`
* $ `gpg -ab apache-airavata-*${project.version}*-bin.tar.gz`
* $ `gpg -ab apache-airavata-*${project.version}*-bin.zip`
* $ `gpg --print-md SHA512 apache-airavata-*${project.version}*-bin.tar.gz > apache-airavata-*${project.version}*-bin.tar.gz.sha`
* $ `gpg --print-md SHA512 apache-airavata-*${project.version}*-bin.zip > apache-airavata-*${project.version}*-bin.zip.sha`
* $ `gpg --print-md MD5 apache-airavata-*${project.version}*-bin.tar.gz > apache-airavata-*${project.version}*-bin.tar.gz.md5`
* $ `gpg --print-md MD5 apache-airavata-*${project.version}*-bin.zip > apache-airavata-*${project.version}*-bin.zip.md5`

Stage the source and binary artifacts to the dist development repository

• Checkout Airavata development dist area:

  `svn co https://dist.apache.org/repos/dist/dev/airavata airavata-dev-dist`
  

• Create the directory for ${project.version} and RC{number} within it. The RC number corresponds to the current release attempt.

• Copy the source and binaries into the dist area.
  • Copy the source and binaries into the development dist RC area created above.
  • Sources and signed artifacts can be downloaded from staging repo https://repository.apache.org/content/groups/staging/org/apache/airavata/airavata/${project.version}.
  • Source artifacts should include airavata-{project.version}-source-release.zip, airavata-{project.version}-source-release.zip.asc, airavata-{project.version}-source-release.zip.sha, airavata-{project.version}-source-release.zip.md5
  • Binaries and gpg signed artifacts from step 11.
  • Verify they are downloadable from https://dist.apache.org/repos/dist/dev/airavata/${project.version}/RC{number}.

• Checkout Airavata development dist area:

  `svn co https://dist.apache.org/repos/dist/dev/airavata airavata-dev-dist`
  

• Create the directory for ${project.version} and RC{number} within it. The RC number corresponds to the current release attempt.

• Copy the source and binaries into dist area.
  • Copy the source and binaries into the development dist RC area created above.
  • Sources and signed artifacts can be downloaded from staging repo https://repository.apache.org/content/groups/staging/org/apache/airavata/airavata/${project.version}.
  • Source artifacts should include airavata-{project.version}-source-release.zip, airavata-{project.version}-source-release.zip.asc, airavata-{project.version}-source-release.zip.sha, airavata-{project.version}-source-release.zip.md5
  • Binaries and gpg signed artifacts from step 11.
  • Verify they are downloadable from https://dist.apache.org/repos/dist/dev/airavata/${project.version}/RC{number}.

1. Create a VOTE email thread on dev@ to record votes as replies, like this
2. Create a DISCUSS email thread on dev@ for any vote questions, this

3. Perform a review of the release and cast your vote. For elaborate instructions, please consult Apache Release FAQ.

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.