+1 binding
* Verified the artifact signatures and digests (I don’t think the MD5 and SHA1
digests need to be published anymore).
* Verified the build process and contrib check.
* Verified the LICENSE and NOTICE files.
* Deployed a NiFi Registry 0.7.0 instance and connected to it with NiFi
1.1
+1 (non-binding)
- Verified checksums, signatures, and commit hash
- Verified README, LICENSE & NOTICE
- Verified full clean build & contrib check on Java 8
- Able to create buckets and versioned flows on non-secure NiFi/Registry
Thanks,
Margot
> On Jul 15, 2020, at 8:31 AM, Bryan Bende wrote:
+1 non-binding.
Verified full clean build with contrib check on Java 8, commit tag and
hash. diffed sources and looked good.
License + Notice looked good.
Ran local docker image and created a few buckets on a non-secure
nifi/registry.
All looks good.
On Wed, Jul 15, 2020 at 3:36 PM Joe Witt wr
Hi,
Reflecting to an ongoing chat conversation about intermediate releases:
I agree with not rushing 1.0, but having multiple releases with big API
changes after 0.8 would be probably difficult for the user base to adopt
to.
A problematic example:
- We make a decision on which namespace a par