HowTo Release Apache Any23

This short guide is for volunteers that intend to cover the role of Release Manager

Prerequisites

  • Install/Configure GPG - The artifacts that are deployed to the ASF central repository need to be signed. To do this you will need to have a public and private keypair. There is a very good guide that will walk you though this.
  • Install Apache Maven 2.2.1 or higher. 2.2.0 has a bug that will produce invalid checksums; we strongly encourage our committers to install the latest Apache Maven

Configuration

Apache Maven

As of Maven 2.1.0 you can now encrypt your servers passwords. We highly recommend that you follow this guide to set your master password and use it to encrypt your ASF password in the next section.

ASF settings

Using the instructions from the previous step encrypt your Sonatype password and add the following servers to your ~/.m2/settings.xml file. You may already have other servers in this file. If not just create the file.

<?xml version="1.0" encoding="UTF-8"?>
<settings>
  ...
  <servers>
    <server>
      <id>apache.snapshots.https</id>
      <username>simonetripodi</username>
      <password>{put your encrypted password here}</password>
    </server>
    <server>
      <id>apache.releases.https</id>
      <username>simonetripodi</username>
      <password>{put your encrypted password here}</password>
    </server>
  </servers>
  ...
  <profiles>
    <profile>
      <id>apache</id>
      <activation>
        <activeByDefault>false</activeByDefault>
      </activation>
      <properties>
        <mavenExecutorId>forked-path</mavenExecutorId>
        <gpg.keyname>19FEA27D</gpg.keyname>\
        <!-- optional -->
        <gpg.passphrase>your-gpg-passphrase</gpg.passphrase>
      </properties>
    </profile>
  </profiles>
  ...
</settings>

You can find a settings.xml template in our Git committers space. Please see here for access to the committers space.

Release steps

Prepare the source for release

  1. Clean up JIRA so the Fix Version in issues resolved since the last release includes this release version correctly. Also, transition any Resolved issues to the Closed state.
  2. Update the text files in a working copy of the project root:
    1. Update the CHANGES based on the Text release reports from JIRA.
    2. Review and update README if needed.
    3. Review and update NOTICE year number if needed. The same goes for all plugins and service NOTICE as well.
    4. Edit the following properties in pom.xml to reflect the proposed release versions of the respective artifacts.
    5. <project...>
        ...
        <properties>
          <latest.stable.released>1.X</latest.stable.released>
        
      </properties>
    6. Commit any changes back to Git origin master branch:
      svn add ...
      git commit -m "updating files for release"
      git push origin master
      .
  3. Perform a full build and deploy the SNAPSHOT artifacts:
    mvn clean deploy

Prepare the release

  1. Do a dry run of the release:prepare step.
    mvn release:prepare -DdryRun=true
    The dry run will not commit any changes back to Git and gives you the opportunity to verify that the release process will complete as expected.

    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.

  2. 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 Git. The only differences between pom.xml.tag and its corresponding pom.xml file should be the version number.
    2. If other formatting changes have been made you should review the changes and then commit them back to Git origin master branch:
      svn add ...
      git commit -m "updating files for release"
      git push origin master
    3. Assuming the .tag files look OK you may proceed and do any other validation you feel necessary. The following list may be helpful:
      1. 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.
      2. Verify signatures: On Un*x platforms the following command can be executed:
        for file in `find . -type f -iname '*.asc'`
        do
          gpg --verify ${file}
        done
        You'll need to look at the output to ensure it contains only good signatures:
        gpg: Good signature from ...
        gpg: Signature made ...
    4. Once any failures or required updates have been committed to svn, rollback the release prepare files:
      mvn release:rollback
  3. Run the release:prepare step for real this time. You'll be prompted for the same version information and optionally your GPG passphrase again.
    mvn release:prepare

Perform the release

  1. From the directory where you have launched release:prepare execute (this step will create a maven staging repository):
    mvn release:perform [-Duser.name=<your_apache_uid>]

    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, and Mac OSX 10.9.2 but unknown for Windows.

    1. Verify the staged artifacts in the Nexus repository:
      1. https://repository.apache.org/
      2. Enterprise --> Staging
      3. Staging tab --> Name column --> org.apache.any23
      4. Navigate through the artifact tree and make sure that all binary, javadoc, sources, and tests jars, as well as poms, ... have .asc (GPG signature) and checksum files (see Repository FAQ and Detached Signatures). The any23-sources-dist-X.Y.tar.gz and any23-sources-dist-X.Y.zip files shall likewise have signature and checksum files.
    2. Close the Nexus staging repo:
      1. https://repository.apache.org/
      2. Enterprise --> Staging
      3. Staging tab --> Name column --> org.apache.any23
      4. Right click on the open org.apache.any23-XXX staging repo and select Close.
    3. Add the distribution artifacts to the build area (the grab-binaries.sh script is versioned under the Any23 Git committers space).
      
      sh grab-binaries.sh REPO_ID ANY23_VERSION CRAWLER_VERSION HTML_SCRAPER_VERSION OFFICE_SCRAPER_VERSION

Vote the Release

  1. Create a VOTE email thread on any23-dev to record votes as replies, e.g.:
    To: "Apache Any23 Developers List" <dev [at] any23.apache.org>
    Subject: [VOTE] Release Apache Any23 X.Y
    
    Hi,
    
    We solved N issues:
    http://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312323&styleName=Html&version=X.Y
    
    There are still a couple of issues left in JIRA:
    http://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&pid=12312323&status=1
    
    Git source tag signature (xyz....):
    https://git-wip-us.apache.org/repos/asf/any23.git......
    
    Staging repo:
    https://repository.apache.org/content/repositories/orgapacheany23-[YOUR REPOSITORY ID]/
    
    Staging binaries:
    https://dist.apache.org/repos/dist/dev/any23/X.Y/
    
    PGP release keys (signed using ABCDEFG):
    http://any23.apache.org/dist/KEYS
    
    Vote will be open for 72 hours.
    
    [ ] +1, let's get it ruuuumbleeeeee!!!
    [ ] +/-0, fine, but consider to fix few issues before...
    [ ] -1, nope, because... (and please explain why)
  2. Create a DISCUSS email thread on any23-dev@ for any vote questions, e.g.:
    To: "Apache Any23 Developers List" <dev [at] any23.apache.org>
    Subject: [DISCUSS] Apache Any23 X.Y
    
    Discussion thread for vote on &lt;version&gt; release candidate, with Git source tag (xyz.....).
    
    For more information on the release process, check out http://www.apache.org/dev/release.html
    
    Some of the things to check before voting are:
     - does "mvn rat:check" pass on the source
     - can you build the contents of source-release.zip and svn tag
     - do all of the staged jars/zips contain the required LICENSE and NOTICE files
     - are all of the staged jars signed and the signature verifiable
     - is the signing key in the project's KEYS file and on a public server (i.e. http://www.apache.org/dist/any23/)
                
  3. Perform a review of the release and cast your vote. For more details on Apache releases see 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" below).
  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, replying to the initial email prepending [RESULT] to the original subject and include a list of every binding +1, 0 and -1 vote.
    To: "Apache Any23 Developers List" <dev [at] any23.apache.org>
    CC: "Apache Any23 PMC List" <private [at] any23.apache.org>
    Subject: [RESULT] [VOTE] Release Apache Any23 X.Y
    
    Hi,
    The vote has passed with the following result :
    
    +1 (binding):
    
        Chris Mattmann
        Lewis John Mcgibbney
        Michele Mostarda
        Simone Tripodi
    
    +1 (non binding):
    
        Mario Rossi
        John Doe
    
    I will promote the artifacts to the central repo.

Finalize the Release

  1. Promote the staged nexus artifacts:
    1. https://repository.apache.org/
    2. Enterprise --> Staging
    3. Staging tab --> Name column --> org.apache.any23
    4. Right click on the closed org.apache.any23-XXX staging repo and select Release.
  2. Add the distribution artifacts to the distribution area
  3. Update the JIRA versions page to 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.

Announce the Release

Make an announcement about the release on the follwoing lists:

  1. user [at] any23.apache.org
  2. dev [at] any23.apache.org
  3. announce [at] apache.org: lists as per the Apache Announcement Mailing Lists page
  4. public-geosemweb [at] w3.org: lists as found here
  5. public-lod [at] w3.org: lists as found here
  6. public-ogsw [at] w3.org: lists as found here
  7. public-owl-wg [at] w3.org: lists as found here
  8. public-rdfa [at] w3.org: lists as found here
  9. public-semnews [at] w3.org: lists as found here
  10. public-semstats [at] w3.org: lists as found here
  11. public-semweb-lifesci [at] w3.org: lists as found here
  12. public-semweb-ui [at] w3.org : lists as found here
  13. public-semwebprog [at] w3.org: lists as found here
  14. public-sodata [at] w3.org: lists as found here
  15. public-ssn-cg [at] w3.org: lists as found here
  16. public-sweo-ig [at] w3.org: lists as found here
  17. public-swim [at] w3.org: lists as found here
  18. public-swisig [at] w3.org: lists as found here
  19. public-ws-semann [at] w3.org: lists as found here
  20. semantic-web [at] w3.org: lists as found here
From: YOUR_APACHE_USERNAME@apache.org
To: "ASF Announcements" <announce [at] apache.org>, "Apache Any23 Users List" <user [at] any23.apache.org>
CC: "Apache Any23 Developers List" <adev [at] any23.apache.org> .....
Subject: [ANNOUNCE] Apache Any23 X.Y

The Apache Any23 Team is pleased to announce the release of Apache Any23 X.Y.

Anything To Triples (any23) is a library, a web service and a command line tool that
extracts structured data in RDF format from a variety of Web documents.

Release Notes:

(put JIRA release notes here)

Have Fun,
(committer name), on behalf of the Apache Any23 PMC

Recovering from a vetoed release

  1. Reply to the initial vote email prepending [CANCELED] to the original subject.
  2. Rollback the version upgrades in trunk by either:
    1. Restore the 0.1-rc1.tar.gz and run
      mvn release:rollback
      or manually revert the versions in trunk to the prior version and commit
  3. Delete the svn tag created by the release:perform step:
    $ git push origin --delete ${branchName}
    $ git branch -d the_local_branch
  4. Drop the Nexus staging repo:
    1. https://repository.apache.org/
    2. Enterprise --> Staging
    3. Staging tab --> Name column --> org.apache.any23
    4. Right click on the closed org.apache.any23-XXX staging repo and select Drop.
  5. Make the required updates that caused the vote to be canceled.
  6. Spin another release attempt!