On 2016-11-29 10:42 (-0800), Aldrin Piri <a...@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:>


# Import keys file:>

gpg --import KEYS>

# Pull down nifi-minifi-cpp-0.1.0 source release artifacts for review:>






# Verify the signature>

gpg --verify nifi-minifi-cpp-0.1.0-source.tar.gz.asc>

# Verify the hashes (md5, sha1, sha256) match the source and what was
provided in the vote email thread>

md5sum nifi-minifi-cpp-0.1.0-source.tar.gz>

sha1sum nifi-minifi-cpp-0.1.0-source.tar.gz>

sha256sum nifi-minifi-cpp-0.1.0-source.tar.gz>

# Untar nifi-minifi-cpp-0.1.0-source.tar.gz>

tar xf nifi-minifi-cpp-0.1.0-source.tar.gz>

# Verify the build works>

Be mindful of the pre-requisites required for the C++ version of MiNiFi,
enumerated in the README and the switching to the CMake build system>

These can vary from system to system and distribution, an example of the
package listing for a recent Ubuntu release is:>

 cmake libboost-dev libxml2-dev libleveldb-dev gcc g++ uuid-dev>

Once the required environment is established, a build can be performed

cd nifi-minifi-cpp-0.1.0-source>

mkdir build>

cd build>

cmake ..>

make package>

# 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 assembly
(nifi-minifi-cpp-0.1.0-bin.tar.gz) found in your build directory>

# Make sure the README, NOTICE, and LICENSE are present and correct>

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

Be mindful of caveats for this initial release, listed in the README.>

For some additional assistance, a package with configuration files for both
a MiNiFI instance and a NiFi instance available at

The provided sample configuration bundle assumes that NiFi is configured to
listen on port 8081 and has 10001 configured for Site to Site's

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

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

Reply via email to