NOTE:

As a streams release manager, you probably want to use the release.sh and publish-rc.sh scripts in the root of apache-streams.

To perform a release manually, or to better understand what’s going on, read the instructions below.

In either case, you’ll need to first refer to Release Setup Information.

Common Release Steps

1. Environment setup for releasing artifacts (same for SNAPSHOTs and releases)

   1. Use the latest Sun 1.8.x JDK
   2. Use Maven 3.3.9 or later
   3. Make sure the Release Setup steps have been performed.

2. Prepare the source for release:

   1. Cleanup JIRA so the Fix Version in issues resolved since the last release includes this release version correctly.
   2. Update the text files in a working copy of the project root -
      1. Update the CHANGELOG based on the Text release reports from JIRA.
      2. Review and update README.md if needed.
      3. Commit any changes back to git
   3. Stage any Roadmap or Release landing pages on the site.

3. Create a release candidate branch from master.

X should start at 1 and increment if early release candidates fail to complete the release cycle.

    git checkout master
    git branch ${project.name}-${project.version}-rcX
    git checkout ${project.name}-${project.version}-rcX

1. Verify the source has the required license headers before trying to release:

   mvn -Papache-release clean apache-rat:check -e -DskipTests
   

2. Do a dry run of the release:prepare step:

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

   • The dry run will not commit any changes back to SCM and gives you the opportunity to verify that the release process will complete as expected. You will be prompted for the following information :

   * Release version - take the default (should be ${project.version})
   * SCM release tag - *DO NOT TAKE THE DEFAULT*  - ${project.artifactId}-${project.version}-rcX
   * New development version - take the default (should be ${project.version}-SNAPSHOT)
   * GPG Passphrase  
   

   • If you cancel a release:prepare before it updates the pom.xml versions, then use the release:clean goal to just remove the extra files that were created.
   • The Maven release plugin checks for SNAPSHOT dependencies in pom’s. It will not complete the prepare goal until all SNAPSHOT dependencies are resolved.

3. Verify that the release process completed as expected

   1. The release plugin will create pom.xml.tag files which contain the changes that would have been committed to SVN. The only differences between pom.xml.tag and it’s corresponding pom.xml file should be the version number.
   2. Check release.properties and make sure that the scm properties have the right version. Sometimes the scm location can be the previous version not the next version.
   3. Verify signatures (Verifying release signatures)

4. Cleanup the release prepare files again:

   mvn -Papache-release release:clean
   

5. Prepare the release

   1. Run the “release:prepare” step for real this time. You’ll be prompted for the same version information.

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

   1. Backup (zip or tar) your local release candidate directory in case you need to rollback the release after the next step is performed.

6. Perform the release

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

       mvn -Papache-release -Darguments='-Dmaven.test.skip.exec=true' release:perform -Dgoals=deploy -DlocalRepoDirectory=. -DlocalCheckout=true
   

   • 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. This is known to work for Linux, but not for Mac and unknown for Windows.*

       -Duser.name=[your_apache_uid]
   

7. Verify the Nexus release artifacts

   1. Verify the staged artifacts in the nexus repo
      • https://repository.apache.org/index.html
      • Staging repositories (under Build Promotion) –> Name column –> org.apache.streams
      • 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
   1. Close the nexus staging repo
      • https://repository.apache.org/index.html
      • Staging repositories (under Build Promotion) –> Name column –> org.apache.streams
      • Click checkbox for the open staging repo (org.apache.streams-XXX) and press Close in the menu bar.

8. Put the release candidate up for a vote

   1. Create a VOTE email thread on dev@ to record votes as replies
   2. Create a DISCUSS email thread on dev@ for any vote questions
   3. Perform a review of the release and cast your vote. See the following for more details on Apache releases http://www.apache.org/dev/release.html
   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.
   6. Promote the staged nexus artifacts
      • https://repository.apache.org/index.html
      • Staging repositories (under Build Promotion) –> Name column –> org.apache.streams
      • Click checkbox of the closed staging repo (org.apache.streams-XXX) and select Release.

9. Complete the release

   1. Copy the source artifacts over to the distribution area

       svn co https://dist.apache.org/repos/dist/release/streams/releases ./streams-releases  (KEEP this directory until after the release process has been completed)
       cd ./streams-releases
       mkdir ${project.version}
       cd ./${project.version}
       wget https://repository.apache.org/content/repositories/releases/org/apache/streams/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip    
       wget https://repository.apache.org/content/repositories/releases/org/apache/streams/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.asc   
       wget https://repository.apache.org/content/repositories/releases/org/apache/streams/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.md5   
       wget https://repository.apache.org/content/repositories/releases/org/apache/streams/${project.name}/${project.version}/${project.name}-${project.version}-source-release.zip.sha1
       svn add ${project.name}-*
       svn commit -m "Committing Source Release for ${project.name}-${project.version}
   

   1. Create an official release tag from the successful release candidate tag.

       git checkout ${project.name}-${project.version}-rcX
       git tag -a ${project.name}-${project.version} -m 'release tag ${project.name}-${project.version}'
       git push origin :refs/tags/streams-project-${project.version}
   

   1. Update the staged website
      • Update the downloads page (downloads.md) to add new version using the mirrored URLs
      • Modify the URL for the prior release to the archived URL for the release
   1. Publish the website (see website)
      • WAIT 24hrs after committing releases for mirrors to replicate
      • Publish updates to the download page
   1. Delete the prior versions
      • Navigate to the release directories checked out in the prior steps
      • Delete the prior release artifacts using the svn delete command
      • Commit the deletion

10. Update the JIRA versions page to close all issues, mark the version as “released”, and set the date to the date that the release was approved. You may also need to make a new release entry for the next release.

11. Announcing the release

    • Make a news announcement on the streams homepage.
    • Make an announcement about the release on the dev@streams.apache.org, and announce@apache.org list as per the Apache Announcement Mailing Lists page)

for file in `find . -type f -iname '*.asc'`
do
    gpg --verify ${file}
done