Thanks for working on this, Bryan.

+1(non-binding).
 - Verified hashes
 - Confirmed a build
 - Started secured NiFi Registry
 - Tested version control operations for some dataflows
 - Browsed public bucket as anonymous user
 - Created a public bucket, and browsed it as anonymous user
 - Used DatabaseFlowPersistenceProvider, and connected to the same external DB 
from two NiFi Registry instances

On 2019/08/21 17:54:48, Bryan Bende <bbe...@apache.org> wrote: 
> Hello,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi Registry nifi-registry-0.5.0.
> 
> The source zip, including signatures, digests, etc. can be found at:
> https://repository.apache.org/content/repositories/orgapachenifi-1147
> 
> The Git tag is nifi-registry-0.5.0-RC1
> The Git commit ID is 8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=8a1901e79b8bb6ef310a9c7d8bf59a3e34b41d16
> 
> Checksums of nifi-registry-0.5.0-source-release.zip:
> SHA256: 804948c2f3d6d32f88c37c1827d1c9c2d1f842f0ef7e7d953d24e76b152a093b
> SHA512: 
> 0ae202b64ad3b3ab3dadb71b9dea210ac4c8eb1cf3922f10a71d175df75ec069e8a039bcc961d1969a6ac7417da4cc5bd4d0cc1e8515d88be6bd55b7c8c9bce9
> 
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/bbende.asc
> 
> KEYS file available here:
> https://dist.apache.org/repos/dist/release/nifi/KEYS
> 
> 28 issues were closed/resolved for this release:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920&version=12345561
> 
> Release note highlights can be found here:
> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.5.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.
> Then please vote:
> 
> [ ] +1 Release this package as nifi-registry-0.5.0
> [ ] +0 no opinion
> [ ] -1 Do not release this package because...
> 

Reply via email to