+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.6 (bc0240f3c744dd6b6ec2920b3cd08dcc295161ae)
Maven home: /Users/fkis/.sdkman/candidates/maven/current
Java version: 1.8.0_362, vendor: Azul Systems, Inc., runtime:
/Users/fkis/.sdkman/candidates/java/8.0.362-zulu/zulu-8.jdk/Contents/Home/jre
Default locale: en_HU, platform encoding: UTF-8
OS name: "mac os x", version: "14.5", 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

Thanks for RMing Pierre!

Regards
Ferenc

On Thu, Jul 4, 2024 at 10:29 PM Joe Witt <[email protected]> wrote:

> +1 binding
>
> On Thu, Jul 4, 2024 at 1:28 PM David Handermann <
> [email protected]>
> wrote:
>
> > +1 binding
> >
> > - Verified signatures and hashes
> > - Ran build using Maven Wrapper 3.9.6
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 1.8.0-412 x86_64
> > - Ran build on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64
> > - Ran NiFi on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64
> > - Ran NiFi on macOS 14.5 with Azul Zulu JDK 21.0.1 Aarch64
> > - Ran NiFi Registry on Ubuntu 22.04 with Azul Zulu JDK 17.0.11 x86_64
> >
> > - Verified NIFI-13429 with EncryptContentPGP and DecryptContentPGP
> > using sample JPEG
> > - Verified NIFI-13464 NiFi Registry starts without issues following
> > deprecation-log dependency adjustments
> >
> > Thanks Pierre!
> >
> > Regards,
> > David Handermann
> >
> > On Wed, Jul 3, 2024 at 7:42 AM Pierre Villard
> > <[email protected]> wrote:
> > >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > NiFi
> > > 1.27.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-1.27.0
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1276
> > >
> > > Git Tag: nifi-1.27.0-RC2
> > > Git Commit ID: e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18
> > > GitHub Commit Link:
> > >
> >
> https://github.com/apache/nifi/commit/e0c4461d90bd4f6e5f2b81765bcff5cd97ed3e18
> > >
> > > Checksums of nifi-1.27.0-source-release.zip
> > >
> > > SHA256:
> 0ac01d54eeceb4a4f4863880bf67dfa71e6a585036c5caf0546c592bf55ced48
> > > SHA512:
> > >
> >
> 675c7750752bf3092061c9eaac39a975955e9bf881e6bee3124c5842738d8c8626b6a551f33ef7a678018bd83e0323c1f0f0d79101255494d8ca91be7fc750f5
> > >
> > > Release artifacts are signed with the following key:
> > >
> > > https://people.apache.org/keys/committer/pvillard.asc
> > >
> > > KEYS file is available on the Apache Distribution Repository:
> > >
> > > https://dist.apache.org/repos/dist/release/nifi/KEYS
> > >
> > > Issues resolved for this version: 37
> > >
> > >
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020&version=12354832
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.27.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-1.27.0
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> >
>

Reply via email to