Still working on the validation, but I was able to get past the point in 0.6.0 on my Windows 10 rig that kept failing in unit tests.
On Wed, Apr 6, 2016 at 5:51 PM, Joe Witt <joew...@apache.org> 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-0.6.1 source release artifacts for review: > > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.asc > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.md5 > wget > https://dist.apache.org/repos/dist/dev/nifi/nifi-0.6.1/nifi-0.6.1-source-release.zip.sha1 > > # Verify the signature > gpg --verify nifi-0.6.1-source-release.zip.asc > > # Verify the hashes (md5, sha1) match the source and what was provided > in the vote email thread > md5sum nifi-0.6.1-source-release.zip > sha1sum nifi-0.6.1-source-release.zip > > # Unzip nifi-0.6.1-source-release.zip > > # Verify the build works including release audit tool (RAT) checks > cd nifi-0.6.1 > 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! >
