+1 (binding)
On Mon, Jan 1, 2018 at 2:20 PM, Jeff <[email protected]> wrote: > +1 (binding) > > - Ran through the helper guide > - Ran through the initial testing steps in the helper guide > - Ran through several use case scenarios, everything worked as expected, > with a minor exception described below. > > NiFi Registry looks great! I think this provides a huge quality of life > improvement for NiFi and its users, and this is only the initial release! > Amazing! > > One thing I did notice, when working with two process groups referencing > the same versioned flow. If one of these process groups is modified (for > example, a processor was added) and the changes are committed, the second > process group will report that it's up to do date, though it doesn't have > any of the changes that were committed. It appears there's a period of > time between the commit of the changes and NiFi's retrieval/integration of > the updates from the registry. Refreshing the NiFi UI during this time > period will still show both process groups as up to date, though the > process group with the second instance of that versioned flow will still > not have the changes. Some moments later, the second process group's icon > will report that there's a new version. Updating that second process group > to the new version works as expected. > > This is minor and doesn't effect NiFi Registry, but I thought I'd mention > it here. I'll post this on the NiFi PR [1] as well. > > [1] https://github.com/apache/nifi/pull/2219. > > On Mon, Jan 1, 2018 at 11:30 AM Andrew Lim <[email protected]> > wrote: > >> +1 (non-binding) >> >> -Ran full clean install on OS X (10.11.6) >> -Tested secure and unsecure Registry instances: creating/editing users, >> buckets, policies, special privileges; performed similar testing on group >> level >> -Reviewed documentation >> -Performed basic testing in NiFi: adding registry clients, putting a >> process group under version control, saving different versions, changing >> versions, importing a version, stopping version control >> >> Awesome initial release for this project! >> >> Drew >> >> >> > On 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... >> >>
