You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by Tony Kurc <tk...@apache.org> on 2016/02/13 00:37:35 UTC

UPDATED Apache NiFi 0.5.0 Release Candidate Helper

Team (including Aldrin),

Here again is guidance to help those interested in validating/verifying the
release so they can vote. Added a step, which is verifying the branch point
for the release.

# Download latest KEYS file:
  https://dist.apache.org/repos/dist/dev/nifi/KEYS

# Import keys file:
  gpg --import KEYS

# [optional] Clear out local maven artifact repository

# Pull down nifi-0.5.0 source release artifacts for review:

  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.asc
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.md5
  wget
https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.sha1

# Verify the signature
  gpg --verify nifi-0.5.0-source-release.zip.asc

# Verify the hashes (md5 and sha1) match the source and what was
provided in the vote email thread
  md5sum nifi-0.5.0-source-release.zip
  sha1sum nifi-0.5.0-source-release.zip

# Unzip nifi-0.5.0-source-release.zip

# Verify the build works including release audit tool (RAT) checks and the
introduced Groovy unit tests
  cd nifi-0.5.0
  mvn clean install -Pcontrib-check,groovy-unit-test

# Verify the contents contain a good readme, NOTICE, and LICENSE.

# Verify the git commit ID is correct

# Verify the RC was branched off the correct git commit ID

# Look at the resulting convenience binary as found in nifi-assembly/target

# Make sure the readme, LICENSE, and NOTICE are present and correct

# Run the resulting convenience binary and make sure it works as expected

# Send a response to the vote thread indicating a +1, 0, -1 based on your
findings.

A much wordier version of this is here:
https://nifi.apache.org/release-guide.html

Thank you for your time and effort to validate the release!

Re: UPDATED Apache NiFi 0.5.0 Release Candidate Helper

Posted by Joe Witt <jo...@gmail.com>.
Recommend *not* running the groovy tests.  They set the groovy
dependency to test scope which means groovy ends up not supported in
the convenience binary.

# Verify the build works including release audit tool (RAT) checks
  cd nifi-0.5.0
  mvn clean install -Pcontrib-check

We should work to get the groovy stuff into the build without needing
profile activation if they should be the norm.

Thanks
Joe

On Fri, Feb 12, 2016 at 6:37 PM, Tony Kurc <tk...@apache.org> wrote:
> Team (including Aldrin),
>
> Here again is guidance to help those interested in validating/verifying the
> release so they can vote. Added a step, which is verifying the branch point
> for the release.
>
> # Download latest KEYS file:
>   https://dist.apache.org/repos/dist/dev/nifi/KEYS
>
> # Import keys file:
>   gpg --import KEYS
>
> # [optional] Clear out local maven artifact repository
>
> # Pull down nifi-0.5.0 source release artifacts for review:
>
>   wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip
>   wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.asc
>   wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.md5
>   wget
> https://dist.apache.org/repos/dist/dev/nifi/nifi-0.5.0/nifi-0.5.0-source-release.zip.sha1
>
> # Verify the signature
>   gpg --verify nifi-0.5.0-source-release.zip.asc
>
> # Verify the hashes (md5 and sha1) match the source and what was
> provided in the vote email thread
>   md5sum nifi-0.5.0-source-release.zip
>   sha1sum nifi-0.5.0-source-release.zip
>
> # Unzip nifi-0.5.0-source-release.zip
>
> # Verify the build works including release audit tool (RAT) checks and the
> introduced Groovy unit tests
>   cd nifi-0.5.0
>   mvn clean install -Pcontrib-check,groovy-unit-test
>
> # Verify the contents contain a good readme, NOTICE, and LICENSE.
>
> # Verify the git commit ID is correct
>
> # Verify the RC was branched off the correct git commit ID
>
> # Look at the resulting convenience binary as found in nifi-assembly/target
>
> # Make sure the readme, LICENSE, and NOTICE are present and correct
>
> # Run the resulting convenience binary and make sure it works as expected
>
> # Send a response to the vote thread indicating a +1, 0, -1 based on your
> findings.
>
> A much wordier version of this is here:
> https://nifi.apache.org/release-guide.html
>
> Thank you for your time and effort to validate the release!