Re: [VOTE] Release Apache NiFi Registry 0.7.0
+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.12.0-SNAPSHOT using current main branch. * Deployed a secure NiFi Registry 0.7.0 instance and connected to it with a secure NiFi 1.12.0-SNAPSHOT instance. Andy LoPresto alopre...@apache.org alopresto.apa...@gmail.com He/Him PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69 > On Jul 16, 2020, at 10:11 AM, Chad Zobrisky 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 wrote: > >> +1 binding. Verified full clean build w contrib check. Sources match >> commit tag. Hashes/Signature good. L looks good. Builds/runs on Java 11. >> Version control to/from NiFi on non secured config. >> >> On Wed, Jul 15, 2020 at 8:32 AM Bryan Bende wrote: >> >>> Hello, >>> >>> I am pleased to be calling this vote for the source release of Apache >> NiFi >>> Registry 0.7.0. >>> >>> The source zip, including signatures, digests, etc. can be found at: >>> https://repository.apache.org/content/repositories/orgapachenifi-1161 >>> >>> The source being voted upon and the convenience binaries can be found at: >>> >>> >> https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.0/ >>> >>> A helpful reminder on how the release candidate verification process >> works: >>> >>> >> https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate >>> >>> The Git tag is nifi-registry-0.7.0-RC1 >>> The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac >>> >>> >> https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac >>> >>> Checksums of nifi-registry-0.7.0-source-release.zip: >>> SHA256: acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8 >>> SHA512: >>> >>> >> 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683 >>> >>> 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 >>> >>> 19 issues were closed/resolved for this release: >>> >>> >> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12346077 >>> >>> Release note highlights can be found here: >>> >>> >> https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.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.7.0 >>> [ ] +0 no opinion >>> [ ] -1 Do not release this package because... >>> >>
Re: [VOTE] Release Apache NiFi Registry 0.7.0
+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: > > Hello, > > I am pleased to be calling this vote for the source release of Apache NiFi > Registry 0.7.0. > > The source zip, including signatures, digests, etc. can be found at: > https://repository.apache.org/content/repositories/orgapachenifi-1161 > > The source being voted upon and the convenience binaries can be found at: > https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.0/ > > A helpful reminder on how the release candidate verification process works: > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > The Git tag is nifi-registry-0.7.0-RC1 > The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac > > Checksums of nifi-registry-0.7.0-source-release.zip: > SHA256: acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8 > SHA512: > 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683 > > 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 > > 19 issues were closed/resolved for this release: > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12346077 > > Release note highlights can be found here: > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.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.7.0 > [ ] +0 no opinion > [ ] -1 Do not release this package because...
Re: [VOTE] Release Apache NiFi Registry 0.7.0
+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 wrote: > +1 binding. Verified full clean build w contrib check. Sources match > commit tag. Hashes/Signature good. L looks good. Builds/runs on Java 11. > Version control to/from NiFi on non secured config. > > On Wed, Jul 15, 2020 at 8:32 AM Bryan Bende wrote: > > > Hello, > > > > I am pleased to be calling this vote for the source release of Apache > NiFi > > Registry 0.7.0. > > > > The source zip, including signatures, digests, etc. can be found at: > > https://repository.apache.org/content/repositories/orgapachenifi-1161 > > > > The source being voted upon and the convenience binaries can be found at: > > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-registry/nifi-registry-0.7.0/ > > > > A helpful reminder on how the release candidate verification process > works: > > > > > https://cwiki.apache.org/confluence/display/NIFI/How+to+help+verify+an+Apache+NiFi+release+candidate > > > > The Git tag is nifi-registry-0.7.0-RC1 > > The Git commit ID is c8f26039712354b94c4d458b7ea491316c6facac > > > > > https://gitbox.apache.org/repos/asf?p=nifi-registry.git;a=commit;h=c8f26039712354b94c4d458b7ea491316c6facac > > > > Checksums of nifi-registry-0.7.0-source-release.zip: > > SHA256: acc6b21444d229d78b8a604750231e1c7e80495c9cccfb59ec043ebe952fd2a8 > > SHA512: > > > > > 428839e0c861095547e328fcfda42cb3f2a87c0b03f7205d6878f8b7267975fe2ad051d4b5f980cac8f47a249c8ee21686c8d909f275454e25d8a654099bd683 > > > > 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 > > > > 19 issues were closed/resolved for this release: > > > > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12320920=12346077 > > > > Release note highlights can be found here: > > > > > https://cwiki.apache.org/confluence/display/NIFIREG/Release+Notes#ReleaseNotes-NiFiRegistry0.7.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.7.0 > > [ ] +0 no opinion > > [ ] -1 Do not release this package because... > > >
Re: [discuss]Release MiNiFi-CPP 0.8.0
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 particular component belongs to and change it for a version 0.9 - We decide to change this again for fixing up the public API with a deadline of 1.0 This would effectively mean that the end users would potentially need to change their codebase to adopt to us getting ready for 1.0. I propose us agreeing only on having a robust v1.0 and plan no intermediate release unless we clearly see its necessity. Cheers, Adam On 2020. 07. 15. 19:30, Joe Witt wrote: "To allow the community some time to finalize the API, I would not rush 1.0 right after 0.8, unless we see that the API is stable and something we can commit to." +1 to that On Wed, Jul 15, 2020 at 10:28 AM Marton Szasz wrote: Hi, +1. There are countless fixes and stability improvements on the main development branch that would benefit the majority of users. Breaking changes: there are some minor API breakages compared to 0.7, but there was an effort to avoid breaking core APIs and the configuration syntax. I agree with Marc that we should allow ourselves more freedom to fix issues even at the cost of breaking APIs, especially before 1.0. To allow the community some time to finalize the API, I would not rush 1.0 right after 0.8, unless we see that the API is stable and something we can commit to. Thanks, regards, Marton On Wed, 15 Jul 2020 at 17:36, Marc Parisi wrote: +1 to 0.8.0. Been keeping up with changes and I think the progress is great. In my opinion the breaking changes are long coming and probably would be appreciated by the community. Arpad are you thinking of going to 1.x? You're discussing 0.8, but is there any reason to not jump to 1.x after that? Thanks, Marc On Wed, Jul 15, 2020 at 10:12 AM Joe Witt wrote: Arpad Yep makes sense. Frankly the 0. versioning gives the flexibility to do these breaking changes during this stage of the lifecycle. Thanks On Wed, Jul 15, 2020 at 7:06 AM Arpad Boda wrote: Hey, Quite a lot of time has passed since the last release and also a lot of improvements and bug fixes have been made (Memleaks fixed, new threadpool, some new processors, etc), so I think it's time for a new release. Another important aspect would be the release of the current state of the source before introducing some breaking changes - which seems to be necessary at this point. What do you think? Thanks, regards, Arpad
