Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Build release artifacts

  • DEV VOTE
    • Verify all of the source is ready for release

      • Able to validate maven install works fine.

      • Verify LICENSE and NOTICE files for the release is updated based on changes in the release

      • Update the release notes

    • Create a tag in the release branch (${release-version}-rc{release-candidate-number}

    • Create the release artifacts using $ant –f release-build.xml -Dranger–release-version=<new-version-number>)

      •  This should create below 4 files in the

        • target/apache-ranger-<version-number>.tar.gz

        • target/apache-ranger-<version-number>.tar.gz.asc
        • target/apache-ranger-<version-number>.tar.gz.sha256
        • target/apache-ranger-<version-number>.tar.gz.sha512Note: Delete the target/apache-ranger-<version-number>.tar.gz.sha256 and target/apache-ranger-<version-number>.tar.gz.sha512 and regenerate using below command from target directory
          • shasum -a 256 apache-ranger-<version-number>.tar.gz > apache-ranger-<version-number>.tar.gz.sha256
          • shasum -a 512 apache-ranger-<version-number>.tar.gz > apache-ranger-<version-number>.tar.gz.sha512
        • verify the singed tarball and checksum file using below command
          • gpg --verify apache-ranger-<version-number>.tar.gz.asc apache-ranger-<version-number>.tar.gz
          • shasum -a 256 -c apache-ranger-<version-number>.tar.gz.sha256
          • shasum -a 512 -c apache-ranger-<version-number>.tar.gz.sha512
    • Upload the release artifacts (4 files from target folder) to svn (https://dist.apache.org/repos/dist/dev/ranger/${new-version}-rc${release-candidate-number})

    • If the signer's key is not in KEYS file in https://dist.apache.org/repos/dist/release/ranger/KEYS, Update the KEYS file to add that the signer key using SVN.

    • Send release VOTE request to dev@ranger.apache.org and private@ranger.apache.org 

    • If VOTE did not go through,

      • Fix the problem and Repeat the “Build release artifacts” steps again

    •  Send vote results to dev@ranger.apache.org , private@ranger.apache.org  via email 

  • IPMC VOTE (This is not required anymore, since Ranger has graduated to a top level project): Update: 30-JAN-2017

...