Joe,
the new guide is great.  One thing that is missing, that I would like to
make sure that I’m doing the same as you all, is how you are verifying
the commit hashes.  Would it be possible to document how you guys are doing
that?


On February 21, 2020 at 22:21:41, Joe Witt (joew...@apache.org) wrote:

Hello,

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

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

The source being voted upon and the convenience binaries can be found at:
https://dist.apache.org/repos/dist/dev/nifi/nifi-1.11.3/

A helpful reminder on how the release candidate verification process works:
https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate

The Git tag is nifi-1.11.3-RC1
The Git commit ID is 10b509cf5bb88b12b0dd497543291f3c49a9903f
https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=10b509cf5bb88b12b0dd497543291f3c49a9903f

Checksums of nifi-1.11.3-source-release.zip:
SHA256: b2544719a8de02892b3436f1e6084b9b6011bf706a183fa2f059a9961634a7bd
SHA512:
353671e06dd60e186d2a9a29eb9b7c2d183757f6a0f76801b4ecb5d87aab99e701b9ebde932ee414d4b304afd2bd1d0a0e574906a385cfafc8de36cc47c2d0a3


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

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

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

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. Then please vote:

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

Reply via email to