+1 (non-binding)

Went through the helper guide, local maven repo cleaned up, full clean
build with contrib check, verified signatures and hashes

Apache Maven 3.9.9 (8e8579a9e76f7d015ee5ec7bfcdc97d260186937)
Maven home: /Users/fkis/.m2/wrapper/dists/apache-maven-3.9.9/3477a4f1
Java version: 21.0.3, vendor: Azul Systems, Inc., runtime:
/Users/fkis/.sdkman/candidates/java/21.0.3-zulu/zulu-21.jdk/Contents/Home
Default locale: en_HU, platform encoding: UTF-8
OS name: "mac os x", version: "14.7.1", arch: "aarch64", family: "mac"

Validations performed:
- Started NiFi, created a simple flow with ListenHTTP and Input Port.
Validated ListenHTTP processor is able to receive data
- Started MiNiFi Java:
  * created a simple GenerateFlowFile -> InvokeHttp flow and
GenerateFlowFile -> RemoteProcessGroup flow and pushed to MiNiFi via
C2 protocol
  * Validated that connectivity between NiFi and MiNiFi works via both
InvokeHTTP and S2S

Smaller issues noticed:
- I did not manage to copy the id of the input port using the
clipboard icon next to port id.
- When highlighted text in a textbox using dark mode, I did not see
any visible changes. Can it be that the highlighting color is the same
as the backgroud color?
The above two are just possibly local/environment related issues, and
are definitely no release stoppers.

Thanks for RMing David!

Regards
Ferenc Kis

On Sun, Dec 22, 2024 at 3:16 PM Matt Gilman <matt.c.gil...@gmail.com> wrote:
>
> +1 (binding)
>
> Ran through release helper and verified signature and hashes. Focused my
> review on recent UI efforts. Specifically the new UpdateAttribute advanced
> UI and the new Copy/Paste capabilities that leverage the system clipboard.
> Those worked as expected. I did, however, note an edge case with the Edit
> Process Group dialog when dealing with a specific configuration of selected
> Parameter Contexts and the users permissions with other available Parameter
> Contexts. I've filed [1] for tracking it.
>
> Thanks for RMing David!
>
> [1] https://issues.apache.org/jira/browse/NIFI-14105
>
> Matt
>
> On Fri, Dec 20, 2024 at 3:46 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 2.1.0.
> >
> > Please review the following guide for how to verify a release candidate
> > build:
> >
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Candidate+Verification
> >
> > The source being voted on the and the convenience binaries are
> > available on the Apache Distribution Repository:
> >
> > https://dist.apache.org/repos/dist/dev/nifi/nifi-2.1.0
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1304/
> >
> > Git Tag: nifi-2.1.0-RC3
> > Git Commit ID: f3af2394f90f2326a3ddacf1bf3a2f3160fbe6a6
> > GitHub Commit Link:
> >
> > https://github.com/apache/nifi/commit/f3af2394f90f2326a3ddacf1bf3a2f3160fbe6a6
> >
> > Checksums of nifi-2.1.0-source-release.zip
> >
> > SHA512:
> > 7ac9bbb6dfbcd97e3b2dacb715e77ad5937d72c7df001164b6917d4c10510a39ca4b3e5a735d8cf682d5ab06f7fc56087ff9fa0ac2488d56e9a9f8a03a7b4020
> >
> > Release artifacts are signed with the following key:
> >
> > https://people.apache.org/keys/committer/exceptionfactory.asc
> >
> > KEYS file is available on the Apache Distribution Repository:
> >
> > https://dist.apache.org/repos/dist/release/nifi/KEYS
> >
> > Issues resolved for this version: 90
> >
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12355215
> >
> > Release note highlights can be found on the project wiki:
> >
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.1.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-2.1.0
> > [] +0 no opinion
> > [] -1 Do not release this package because...
> >

Reply via email to