...

Introduction

Thanks for your interest in helping to vote on a release candidate. First it is a good idea to review http://nifi.apache.org/release-guide.html. This page provides important background material to understand the mechanics and meaning of a release. It explains how things like +1, -1, 0, binding, and non binding votes work. With the above in mind lets dive right into the main steps in reviewing a release candidate of Apache NiFi (note the steps for NiFi Registry, MiNiFi, etc.. may differ).
Please find the associated guidance to help those interested in validating/verifying the release so they can vote.

...

!

Please review the Project Release Guide for details on the release process and procedures associated with voting.

Prerequisites

Download OpenPGP Keys for Signature Verification

wget https://dist.apache.org/repos/dist/devrelease/nifi/KEYS

wget for Windows can be found here.

Import

...

OpenPGP Keys

gpg --import KEYS

On Windows cmder includes gpg.

[

...

Optional] Clear

...

Local Maven Artifact Repository

rm -rf ~/.m2/repository/*

...

Verification Steps

Download Source Release Files

export VERSION=2.3.0

wget https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1$VERSION/nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zip
wget wget https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1$VERSION/nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zip.asc
wget wget https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1
wget https://dist.apache.org/repos/dist/dev/nifi/nifi-nar-maven-plugin-1.5.1/nifi-nar-maven-plugin-1.5.1-$VERSION/nifi-nar-maven-plugin-1.5.1-source-release.zip.sha256$VERSION-source-release.zip.sha512

Verify

...

OpenPGP Signatures

gpg --verify -v nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zip.asc

Verify

...

Hashes Match Source Release Files and Vote Email Thread

Run the following commands on Linux or macOS:

shasum -a

...

shasum -a 256 nifi-nar-maven-plugin-1.5.1-source-release.zip
shasum -a 512 nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zipOn

Run the following commands on Windows:

certutil -hashfile nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zip SHA256
certutil -hashfile nifi-nar-maven-plugin-1.5.1-source-release.zip SHA512

...

SHA512

Extract Source Release Files

unzip -DD nifi-nar-maven-plugin-1.5.1$VERSION-source-release.zip

Verify

...

Maven Build with Licensing and Style Checks

Use Maven Wrapper to build using the currently configured Maven version. The Maven Wrapper script is named mvnw for Linux and macOS, and mvnw.cmd for Windows.

cd nifi-nar-maven-plugin-1.5.1
mvn -T 1C clean install

...

$VERSION

On Linux or macOS

./mvnw clean verify

On Windows

mvnw.cmd clean verify


Verify Additional Source and Build Artifacts

• 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
  
• Verify that the NiFi project can build NARs correctly using the new version of the plugin:
  • Update NiFi's root pom to use version 1.5.1 of the plugin: https://github.com/apache/nifi/blob/main/pom.xml#L101
  • Perform a build of NiFi, optionally clear out local .m2 repo mvn clean install
  • Ensure that NiFi starts and loads all processors, controller services, and reporting tasks
  Spot check a few NARs to ensure they include META-INF/docs/extension-manifest.xml
  • cp NIFI_HOME/lib/nifi-xyz-bundle.nar /tmp
  • cd /tmp unzip nifi-xyz-bundle.nar
  cat META-INF/docs/extension-manifest.xml
  • the nifi.nar.maven.plugin.version property to match the release candidate version
  • Run a build of the NiFi project
  • Verify that NiFi starts with one or more Processors and other extension components

Send Response to Vote Thread

The team welcomes participation in the release verification process! Project Management Committee members can cast binding votes. All other committers and contributors can cast non-binding votes.

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!