Apache NiFi 1.0.0 RC1 Release Helper Guide

[Joe Percivall <jo...@yahoo.com.INVALID>]

Hello Apache NiFi community,

Please find the associated guidance to help those interested in validating/verifying the release so they can vote.

# 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-1.0.0 source release artifacts for review:

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

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

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

# Unzip nifi-1.0.0-source-release.zip

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

# 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, NOTICE, and LICENSE 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.

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

Re: Apache NiFi 1.0.0 RC1 Release Helper Guide

[Yolanda Davis <yo...@gmail.com>]

+1 (non-binding)

Ran full test suite, with rat and contrib-check.  Verified, readme, notice,
license, commit ID, hashes and checksums. Tested flows and templates in
standalone cluster (on Mac OS).

On Fri, Aug 26, 2016 at 12:26 PM, Joe Percivall <
joepercivall@yahoo.com.invalid> wrote:

> Hello Apache NiFi community,
>
> Please find the associated guidance to help those interested in
> validating/verifying the release so they can vote.
>
> # 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-1.0.0 source release artifacts for review:
>
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.asc
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.md5
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.sha1
> wget https://dist.apache.org/repos/dist/dev/nifi/1.0.0/nifi-1.0.
> 0-source-release.zip.sha256
>
> # Verify the signature
> gpg --verify nifi-1.0.0-source-release.zip.asc
>
> # Verify the hashes (md5, sha1, sha256) match the source and what was
> provided in the vote email thread
> md5sum nifi-1.0.0-source-release.zip
> sha1sum nifi-1.0.0-source-release.zip
> sha256sum nifi-1.0.0-source-release.zip
>
> # Unzip nifi-1.0.0-source-release.zip
>
> # Verify the build works including release audit tool (RAT) checks
> cd nifi-1.0.0
> mvn clean install -Pcontrib-check
>
> # 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, NOTICE, and LICENSE 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.
>
> Thank you for your time and effort to validate the release!
>



-- 
--
yolanda.m.davis@gmail.com
@YolandaMDavis