+1 - Verified checksums and signatures - Successfully built and ran contrib-check w/ Oracle JDK 1.8.0_152 - Setup the registry w/ NIFI-4436 - Had some fun versioning PGs and rolling back and forth
Note: I ran into some trouble rolling back flows that include new funnels. It always results in an IllegalStateException with 'Funnel <ID> is the destination of another component'. There aren't any problems creating a new PG via Import or rolling forward a flow that newly includes a funnel. Will open an issue. On Dec 29, 2017, 1:56 PM -0600, Yolanda Davis <[email protected]>, wrote: > +1, binding > > Have been looking forward to this contribution; it is a great addition to > the community! > > Following the release helper I verified signatures, hashes as well as > the README, > NOTICE, and LICENSE. Successfully built the project per instructions and > built the NiFi project using the referenced PR. From there I tested in > unsecured mode the basic test suggested in the helper guide. Also tried > minor things such as deleting a flow from registry that was associated to a > PG to ensure NiFi updated as expected. > > One thing that would be helpful is additional documentation on the NiFi > side on how to integrate with Registry. I also noticed on my test to delete > a flow where it seemed there was a pretty big lag when NiFi recognized the > change, even beyond my attempt to refresh. Not sure if this is > configurable or just odd behavior on my end. > > Another minor issue is when someone adds a process group, enters a name for > it and then selects import to use a flow in registry. The name gets > overwritten by the flow (which makes sense) but wondering if there's a way > to either allow user to keep new name or at least let them know it will be > overwritten by version in registry? > > Again great job! > > -yolanda > > > > On Thu, Dec 28, 2017 at 1:09 PM, Bryan Bende <[email protected]> wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > > NiFi Registry 0.1.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1115/ > > > > The Git tag is nifi-registry-0.1.0-RC1 > > The Git commit ID is 81b99e7b04491eabb72ddf30754053ca12d0fcca > > https://git-wip-us.apache.org/repos/asf?p=nifi-registry.git;a=commit;h= > > 81b99e7b04491eabb72ddf30754053ca12d0fcca > > > > Checksums of nifi-registry-0.1.0-source-release.zip: > > MD5: 56244c3c296cdc9c3fcc6d22590b80d1 > > SHA1: 6354e91f868f40d6656ec2467bde307260ad63ca > > SHA256: 2c680e441e6c4bfa2381bf004e9b19a6a79401a6a83e04597d0a714a95efd301 > > > > 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 > > > > 65 issues were closed/resolved for this release: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa? > > projectId=12320920&version=12340217 > > > > Release note highlights can be found here: > > https://cwiki.apache.org/confluence/display/NIFI/ > > Release+Notes#ReleaseNotes-NiFiRegistry0.1.0 > > > > The vote will be open for 96 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-registry-0.1.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > > > > > -- > -- > [email protected] > @YolandaMDavis
