THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
gpg -a -b --digest-algo=SHA512 ${artifact};
echo “Generating md5sum hash”;
md5sum ${artifact} | cut -d" " -f1 > ${artifact}.md5
echo “Generating sha1sum hash”;
gsha1sum ${artifact} | cut -d" " -f1 > ${artifact}.sha1
...
- ASCII armored GPG signatures (--digest-algo=SHA512 select the SHA512 hash algorithm). Configure GPG to always prefer stronger hashes.
$ gpg -a -b --digest-algo=SHA512 nifi-${MINIFI_VERSION}-source-release.zip # produces nifi-${MINIFI_VERSION}-source-release.zip.asc
$ gpg -a -b --digest-algo=SHA512 nifi-${MINIFI_VERSION}-bin.tar.gz # produces nifi-${MINIFI_VERSION}-bin.tar.gz.asc
$ gpg -a -b --digest-algo=SHA512 nifi-${MINIFI_VERSION}-bin.zip # produces nifi-${MINIFI_VERSION}-bin.zip.asc - Generate md5 SHA1 hash summaries.
$ md5sum sha1sum nifi-${MINIFI_VERSION}-source-release.zip | cut -d" " -f1 > > nifi-${MINIFI_VERSIONRELEASAE}-source-release.zip.md5sha1
$ md5sum sha1sum nifi-${MINIFI_VERSION}-bin.tar.gz | cut -d" " -f1 > > nifi-${MINIFI_VERSIONRELEASAE}-bin.tar.gz.md5sha1
$ md5sum sha1sum nifi-${MINIFI_VERSION}-bin.zip | cut -d" " -f1 > > nifi-${MINIFI_VERSIONRELEASAE}-bin.zip.md5sha1 - Generate SHA1 SHA256 hash summaries.
$ sha1sum shasum -a 256 nifi-${MINIFI_VERSION}-source-release.zip | cut -d" " -f1 > nifi-${RELEASAEMINIFI_VERSION}-source-release.zip.sha1sha256
$ sha1sum shasum -a 256 nifi-${MINIFI_VERSION}-bin.tar.gz | cut -d" " -f1 > nifi-${RELEASAE}-bin.tar.gz.sha1
$ sha1sum nifi-${MINIFI_VERSION}-bin.zip | cut -d" " -f1 > nifi-${RELEASAE}-bin.zip.sha1tar.gz.sha256Generate SHA256 hash summaries.
$ shasum -a 256 nifi-${MINIFI_VERSION}-source-releasebin.zip | cut -d" " -f1 > nifi-${MINIFI_VERSION}-source-releasebin.zip.sha256$ shasum -a 256 nifi-${MINIFI_VERSION}-bin.tar.gz | cut -d" " -f1 > nifi-${MINIFI_VERSION}-bin.tar.gz.sha256
$ shasum -a 256 nifi-${MINIFI_VERSION}-bin.zip | cut -d" " -f1 > nifi-${MINIFI_VERSION}-bin.zip.sha256
- ASCII armored GPG signatures (--digest-algo=SHA512 select the SHA512 hash algorithm). Configure GPG to always prefer stronger hashes.
- For reviewing of the For reviewing of the release candidate, commit the source release and convenience binaries files along with their hashes and signatures to https://dist.apache.org/repos/dist/dev/nifi/nifi-minifi-cpp/${VERSION}
...
- RM sends a vote request email to the NiFi Developers Mailing List.
- TO: dev@nifi.apache.org
- FROM: ${RM_USERID}@apache.org
- SUBJECT: [VOTE] Release Apache NiFi MiNiFi C++ ${MINIFI_VERSION}
Hello,
I am pleased to be calling this vote for the source release of Apache NiFi nifi-${MINIFI_VERSION}.
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-nnnn
The Git tag is nifi-${NIFI_VERSION}-RC${RC}
The Git commit ID is <40-BYTE-COMMIT-HASH>
https://git-wip-us.apache.org/repos/asf?p=nifi.git;a=commit;h=<40-BYTE-COMMIT-HASH>
Checksums of nifi-x.y.z-source-release.zip:
MD5: <32-BYTE-MD5SUM-HASH>
SHA1: <40-BYTE-SHA1SUM-HASH>
Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/${RM_USERID}.asc
KEYS file available here:
https://dist.apache.org/repos/dist/release/nifi/KEYS
8 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12329307
Release note highlights can be found here:
https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version${NIFI_VERSION}
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-${NIFI_VERSION}
[ ] +0 no opinion
[ ] -1 Do not release this package because because...
- RM sends the following helper email to the NiFi Developers Mailing List.
- TO: dev@nifi.apache.org
- FROM: ${RM_USERID}@apache.org
- SUBJECT: Apache NiFi ${NIFI_VERSION} RC${RC} Release Helper Guide
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-${NIFI_VERSION} source release artifacts for review:
wget .
# Download latest KEYS file:
https://dist.apache.org/repos/dist/release/nifi/nifi-minifi-cpp/${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}-source-release.zipdev/nifi/KEYS
# Import keys file:
gpg --import KEYS
# [optional] Clear out local maven artifact repository
# Pull down nifi-${NIFI_VERSION} source release artifacts for review:
wget https://dist.apache.org/repos/dist/release/nifi/nifi-minifi-cpp/${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}-source-release.zip.asc
wget https://dist.apache.org/repos/dist/release/nifi/nifi-minifi-cpp/${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}-source-release.zip.md5asc
wget https://dist.apache.org/repos/dist/release/nifi/nifi-minifi-cpp/${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}-source-release.zip.sha1
wget https://dist.apache.org/repos/dist/release/nifi/nifi-minifi-cpp/${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}/nifi-minifi-cpp-${MINIFI_VERSION}-source-release.zip.sha256
# Verify the signature
gpg --verify nifi-${MINIFI_VERSION}-source-release.zip.asc
# Verify the hashes (md5, sha1, sha256) match the source and what was provided in the vote email thread
md5sum nifi-${MINIFI_VERSION}-source-release.zip
sha1sum nifi-${MINIFI_VERSION}-source-release.zip
sha256sum nifi-${MINIFI_VERSION}-source-release.zip
# Unzip nifi-minifi-cpp${MINIFI_VERSION}-source-release.zip
# Verify the build works including release audit tool (RAT) checks
cd nifi-minifi-cpp-${MINIFI_VERSION}
mkdir build && cd build && cmake .. && make package make test && make linter
# 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/targetin
# 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!
- Developers in the community review the release candiate and reply to the vote email with their vote.
- After 72 hours if
- at least 3 binding (PMC members) cast +1 votes, and
- the positive binding votes out number any negative binding votes
- the vote passes and the release candidate is officially released. If the vote does not pass, corrections are made on the release branch and a new release candidate is put forward for a new vote.
- RM sends vote result email.
- TO: dev@nifi.apache.org
- FROM: ${RM_USERID}@apache.org
- SUBJECT: [RESULT][VOTE] Release Apache NiFi MiNiFi C++ ${NIFI_VERSION}
Apache NiFi Community,
I am pleased to announce that the ${NIFI_VERSION} release of Apache NiFi MiNiFi C++ passes with
X +1 (binding) votes
Y -1 (binding) votes
0 0 votes
0 -1 votes
Thanks to all who helped make this release possible.
Here is the PMC vote thread: ${VOTE_THREAD_URL}
...
Hashes
...
sha1sum: 5b3797924eee1a59421ff216c542cb28c3564bfe
sha256sum: 9323165a2086053f8d1ad5478e2b7cc97f01fbc38ba133afe77badba1a446833
...