+1 (binding)

Went through the usual steps. Deployed a secured cluster with secured NiFi
Registry in GCP. Deployed usual/common flows. Looking good to me.

Thanks Joe for taking care of this release.

Pierre

Le jeu. 28 avr. 2022 à 00:52, Peter Turcsanyi <turcsa...@apache.org> a
écrit :

> +1 (non-binding)
>
> Ran through the release helper. Built NiFi on Ubuntu 20.04 with Java 8
> (jdk8u322-b06) and Java 11 (jdk-11.0.14.1+1).
>
> Tested Stateless NiFi via ExecuteStateless and Kafka Connector using Java
> 8, 11 and 17 runtimes. Verified:
>  - NIFI-9834: ExecuteStateless fails when the output FlowFile has no
> content
>  - NIFI-9861: Stateless ClassLoader isolation does not work on Java 11
>
> Regards,
> Peter Turcsanyi
>
> On Wed, Apr 27, 2022 at 9:02 PM Nathan Gough <thena...@apache.org> wrote:
>
> > +1 (non-binding), ran a 3 node cluster using external ZK with some simple
> > test flows. Ran NiFi with Google OIDC auth. Checked hashes and other
> files.
> >
> > On Wed, Apr 27, 2022 at 10:24 AM Mike Thomsen <mikerthom...@gmail.com>
> > wrote:
> >
> > > +1 (binding) Ran a simple tika extraction flow on PDFs and DOCX files.
> > > Worked fine. Saved that flow into the NiFi Registry.
> > >
> > > On Tue, Apr 26, 2022 at 4:47 PM Matt Burgess <mattyb...@gmail.com>
> > wrote:
> > > >
> > > > +1 (binding)
> > > >
> > > > Ran through release helper, tested various flows including version
> > > > control with the Registry, InvokeScriptedProcessor, Relationship
> > > > retry, etc.  I did create [1] for MiNiFi but since there's a
> > > > workaround it's not a dealbreaker IMO, I'm already working on it for
> > > > 1.17.0.
> > > >
> > > > Thanks for RM'ing Joe!
> > > >
> > > > [1] https://issues.apache.org/jira/browse/NIFI-9967
> > > >
> > > > On Mon, Apr 25, 2022 at 2:29 PM Joe Witt <joew...@apache.org> wrote:
> > > > >
> > > > > Hello,
> > > > >
> > > > > I am pleased to be calling this vote for the source release of
> Apache
> > > NiFi
> > > > > 1.16.1.
> > > > >
> > > > > The source zip, including signatures, digests, etc. can be found
> at:
> > > > >
> > https://repository.apache.org/content/repositories/orgapachenifi-1200
> > > > >
> > > > > The source being voted upon and the convenience binaries can be
> found
> > > at:
> > > > > https://dist.apache.org/repos/dist/dev/nifi/nifi-1.16.1/
> > > > >
> > > > > 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-1.16.1-RC1
> > > > > The Git commit ID is 81166797e552b9d14b482807632f2f04321b2018
> > > > >
> > >
> >
> https://gitbox.apache.org/repos/asf?p=nifi.git;a=commit;h=81166797e552b9d14b482807632f2f04321b2018
> > > > >
> > > > > Checksums of nifi-1.16.1-source-release.zip:
> > > > > SHA256:
> > > 2c39b45ba8eec42d601d5c9facad623d14660dd209c011b4a13b2b559b9f3e32
> > > > > SHA512:
> > > > >
> > >
> >
> cd670ab558937cac709dea0b4be3351559f57c9e9aedf54d5153706eee386a021262ef199e2bf9485763cf955931edfd6a24ca1c5a0748a77e3eeb91c490cbda
> > > > >
> > > > > Release artifacts are signed with the following key:
> > > > > https://people.apache.org/keys/committer/joewitt.asc
> > > > >
> > > > > KEYS file available here:
> > > > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > > > >
> > > > > 83 issues were closed/resolved for this release:
> > > > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12351504
> > > > > Release note highlights can be found here:
> > > > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.16.1
> > > > >
> > > > > 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-1.16.1
> > > > > [ ] +0 no opinion
> > > > > [ ] -1 Do not release this package because...
> > >
> >
>

Reply via email to