Thanks for all your efforts, Joe. 

I have one question. The version of the generated package is 
nifi-1.7.0-SNAPSHOT. Is this correct at this stage? If it's ok, +1(non-binding).

 - Succeeded "mvn -T 2.0C clean install -DskipTests -Prpm"
 - Started secure cluster mode
 - Verified sample dataflows work fine
 - Verified the whitelist feature(NIFI-4761) works fine

-Takanobu Asanuma

-----Original Message-----
From: Joe Witt [mailto:joew...@apache.org] 
Sent: Friday, March 23, 2018 1:12 AM
To: dev@nifi.apache.org
Subject: [VOTE] Release Apache NiFi 1.6.0

Hello,

I am pleased to be calling this vote for the source release of Apache NiFi 
nifi-1.6.0.

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1122

The Git tag is nifi-1.6.0-RC1
The Git commit ID is 49a71f4740c9fac38958961f78dd3cde874b0e45
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=49a71f4740c9fac38958961f78dd3cde874b0e45

Checksums of nifi-1.6.0-source-release.zip:
SHA1: 4fb82f386a0aa83614cc01449e540527443811ce
SHA256: 4df6638ec87a5bee12e7978abc64137ee5da5fc8c399e34cf34ca1c3720ac891
SHA512: 
6fa536f9618c6c153c04df5db59913eaf3dd54ae2389368129ac6237f75519e1eee7ba0ca70145a95de01517a1c3ea1f36975895d9d72bb04abb56b7934e013a

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/joewitt.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS

135 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12342422

Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.6.0

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items 
including checking hashes, signatures, build from source, and test.  The please 
vote:

[ ] +1 Release this package as nifi-1.6.0 [ ] +0 no opinion [ ] -1 Do not 
release this package because...

Reply via email to