Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M1 (RC1)

[David Handermann]

Dan,

Thanks for highlighting the Jira issue NIFI-10792 in relation to the
ConvertExcelToCSVProcessor being removed.

Although the Processor was removed in a subsequent issue, including
NIFI-10792 is still important because the incremental code changes are
part of the release version. Those code changes included version
updates, which is another reason for including the issue in the
release version.

Regards,
David Handermann

On Wed, Nov 15, 2023 at 2:11 PM Dan S  wrote:
>
> David,
>  I would like to note one thing regarding the release notes. The following
> tickets are listed
>
>- [NIFI-10792 ] -
>ConvertExcelToCSVProcessor : Failed to convert file over 10MB
>- [NIFI-12100 ] -
>Remove ConvertExcelToCSVProcessor
>
>
> I don't think it makes sense to list NIFI-10792 since the
> ConvertExcelToCSVProcessor
> has been removed with NIFI-12100.
>
> On Wed, Nov 15, 2023 at 3:06 PM David Handermann <
> exceptionfact...@apache.org> wrote:
>
> > Team,
> >
> > Thanks for the votes thus far.
> >
> > Unfortunately one of the new NAR files, nifi-shared-standard-nar did
> > not include the required LICENSE and NOTICE files. This has been
> > corrected in NIFI-12373 [1]. I am cancelling 2.0.0-M1 RC1 and will be
> > preparing a new release candidate build soon.
> >
> > Regards,
> > David Handermann
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-12373
> >
> > On Wed, Nov 15, 2023 at 6:33 AM Csaba Bejan  wrote:
> > >
> > > +1 (binding)
> > >
> > > - Went through the helper guide and did a clean build
> > > - Verified signatures and hashes
> > > - Built on OSX 13.5.2
> > > - Java version: Zulu21.28+85-CA (build 21+35)
> > > - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> > >
> > > - Started NiFi and created a simple flow
> > > - Started MiNiFi and verified integration with C2 Server. Played around
> > with the C2 protocol.
> > >
> > > Verified:
> > > - NIFI-11514 MiNiFi Flow JSON support and deprecating YAML format.
> > Migration tool from YAML to JSON
> > > - NIFI-12333 MiNiFi property override through env and system variables
> > > - NIFI-12335 Fix MiNiFi startup issue
> > >
> > > Thanks for RM'ing, David!
> > >
> > > Regards,
> > > Csaba
> > >
> > > > On 2023. Nov 14., at 1:58, David Handermann <
> > exceptionfact...@apache.org> wrote:
> > > >
> > > > Team,
> > > >
> > > > I am pleased to be calling this vote for the source release of Apache
> > > > NiFi 2.0.0-M1.
> > > >
> > > > 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.0.0-M1
> > > >
> > > > The build artifacts are available on the Apache Nexus Repository:
> > > >
> > > > https://repository.apache.org/content/repositories/orgapachenifi-1236
> > > >
> > > > Git Tag: nifi-2.0.0-M1-RC1
> > > > Git Commit ID: 0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> > > > GitHub Commit Link:
> > > >
> > https://github.com/apache/nifi/commit/0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> > > >
> > > > Checksums of nifi-2.0.0-M1-source-release.zip
> > > >
> > > > SHA256:
> > ba870d51e2362c2f07935634e30d469cb90cd71a65cc4ea205760a2192551696
> > > > SHA512:
> > bc25e1b1d27477950490e250297e74ec969b2ab1b351f318d0908e6c579e919972be5470acc9e147ea87a6185951c5c4f2d22d8f532eab0b045a2d7b922ad594
> > > >
> > > > 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: 934
> > > >
> > > >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599
> > > >
> > > > Release note highlights can be found on the project wiki:
> > > >
> > > >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1
> > > >
> > > > 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.0.0-M1
> > > > [] +0 no opinion
> > > > [] -1 Do not release this package because...
> > >
> >

Re: Removing JRuby?

[Matthew Hawkins]

Hi Team,

As a user I think re-implementing certain scripting languages in Java is a
bad idea compared to having a robust API that any language current or
future can interface with. I make a lot of use of ExecuteProcess and
anecdotally haven't experienced a situation where externally running the
script vs the internal ExecuteScript made a poomteenth of difference in
load or timing. It may have been the case in the 1980's that forking a
process was time consuming; we've moved on.

I think we have (almost) enough options now to expedite data transfer with
an external system so it wouldn't even be necessary to bloat out data sizes
4x with encoded JSON via the REST API, just load flowfiles in via Kafka or
whatever to and from the script. It is no longer your concern; NiFi exposed
the ability to in a generic way and you're done. Stop worrying about things
out of your control like the only available java version of ruby has a
billion and 1 CVE's and is unmaintained, or Jython has a working 3.x
version but it's been labelled "beta" for 15 years. You shouldn't have to
care what a user uses to interface with the NiFi API, and certainly don't
bloat the NiFi installer by including each and every option!

Let someone else write a native API library in scripting language of choice
to expose eg "from NiFi import FlowFileQueue" so an even more expansive
library is available than what was exposed via ExecuteScript. This is what
friends on GitHub are for 
Concentrate on making the NiFi API robust, complete and performant.

(I know the REST API exists, to me the missing piece is being able to
register a script in a generic fashion so that it integrates with the flow
and hence understands which IDs it requires to call esp FlowFile Queues via
the rest API without having to always trawl through eg /flow and
dynamically generate it that way, which would be expensive imo on each
schedule)

Kind regards,


On Thu, 16 Nov 2023, 08:07 Joe Witt,  wrote:

> Team,
>
> Coming back to this as I've been reviewing all the great output of OWASP
> that we're getting daily now (thanks David) as well as some findings from a
> nice vendor tool by JFrog.  And what is popping up left and right are
> issues in terms of vulnerabilities tied to Jython-standalone.  It is very
> clear this component needs to go and is not actively maintained.  It is
> also as noted tied to Python 2 which is eol.  I'll file a JIRA to deprecate
> in 1.x and remove in 2.x.
>
> The discussion about Javascript/Ruby, etc.. I think the best course going
> forward is a specific component appropriate to each desired mechanism is
> introduced in 2.x as interest/effort dictates.  The native Python support
> will eliminate the need for Jython obviously so not worried about that
> coming back.
>
> Thanks
>
> On Tue, Nov 7, 2023 at 5:17 AM Mike Thomsen 
> wrote:
>
> > Matt,
> >
> > I don't use JRuby, but the reason it raised my eyebrow a little was that
> > AFAIK JRuby is the complete opposite of Jython in terms of enterprise
> > readiness and parity with its C-based counterpart.
> >
> > Edward,
> >
> > The problem with Lua here is that the Java versions of Lua aren't being
> > maintained. I think the most recent release on any branch of them was 3
> > years ago. They're basically dead in the water as projects.
> >
> > On Mon, Nov 6, 2023 at 2:57 PM Edward Armes 
> > wrote:
> >
> > > While I do like the ExecuteScript processors as they are great at
> digging
> > > you out of a hole. The performance of them isn't that great.
> > >
> > > That being said I would ve careful about dropping Lua support as there
> > is a
> > > growing list of software that supports end user/administrator
> extensions
> > > via Lua for those that don't want to have to re-compile software
> > > themselves. On the other hand given that Jython doesn't yet have a
> > Python 3
> > > implementation it could be argued dropping Jython support is a must
> given
> > > that the Python 2.x line is basically end of life.
> > >
> > > Now I wonder if its worth re-factoring the ExecuteScript processors to
> be
> > > per language implementations inheriting from a common base like a few
> > > processors do already.
> > >
> > > Edward
> > >
> > > On Mon, 6 Nov 2023, 16:24 Matt Burgess,  wrote:
> > >
> > > > I believe it is because in both ExecuteScript and ExecuteGroovyScript
> > > > you can do "regular" groovy, but EGS has extra built-ins such as easy
> > > > access to controller services, Groovy SQL stuff, etc, and we could
> > > > keep building it out. But IMO we'd have to port the rest of the
> > > > scripted components (ScriptedReader/Writer, etc.) over to the Groovy
> > > > bundle and make sure there's a drop-in replacement in the Python
> stuff
> > > > before we'd want to deprecate the scripted bundle.
> > > >
> > > > On the JRuby front, is that something you use actively? This question
> > > > is for you and the entire community of course.
> > > >
> > > > Regards,
> > > > Matt
> > > >
> > > > On Mon, Nov 6, 2023 

Re: Removing JRuby?

[Joe Witt]

Team,

Coming back to this as I've been reviewing all the great output of OWASP
that we're getting daily now (thanks David) as well as some findings from a
nice vendor tool by JFrog.  And what is popping up left and right are
issues in terms of vulnerabilities tied to Jython-standalone.  It is very
clear this component needs to go and is not actively maintained.  It is
also as noted tied to Python 2 which is eol.  I'll file a JIRA to deprecate
in 1.x and remove in 2.x.

The discussion about Javascript/Ruby, etc.. I think the best course going
forward is a specific component appropriate to each desired mechanism is
introduced in 2.x as interest/effort dictates.  The native Python support
will eliminate the need for Jython obviously so not worried about that
coming back.

Thanks

On Tue, Nov 7, 2023 at 5:17 AM Mike Thomsen  wrote:

> Matt,
>
> I don't use JRuby, but the reason it raised my eyebrow a little was that
> AFAIK JRuby is the complete opposite of Jython in terms of enterprise
> readiness and parity with its C-based counterpart.
>
> Edward,
>
> The problem with Lua here is that the Java versions of Lua aren't being
> maintained. I think the most recent release on any branch of them was 3
> years ago. They're basically dead in the water as projects.
>
> On Mon, Nov 6, 2023 at 2:57 PM Edward Armes 
> wrote:
>
> > While I do like the ExecuteScript processors as they are great at digging
> > you out of a hole. The performance of them isn't that great.
> >
> > That being said I would ve careful about dropping Lua support as there
> is a
> > growing list of software that supports end user/administrator extensions
> > via Lua for those that don't want to have to re-compile software
> > themselves. On the other hand given that Jython doesn't yet have a
> Python 3
> > implementation it could be argued dropping Jython support is a must given
> > that the Python 2.x line is basically end of life.
> >
> > Now I wonder if its worth re-factoring the ExecuteScript processors to be
> > per language implementations inheriting from a common base like a few
> > processors do already.
> >
> > Edward
> >
> > On Mon, 6 Nov 2023, 16:24 Matt Burgess,  wrote:
> >
> > > I believe it is because in both ExecuteScript and ExecuteGroovyScript
> > > you can do "regular" groovy, but EGS has extra built-ins such as easy
> > > access to controller services, Groovy SQL stuff, etc, and we could
> > > keep building it out. But IMO we'd have to port the rest of the
> > > scripted components (ScriptedReader/Writer, etc.) over to the Groovy
> > > bundle and make sure there's a drop-in replacement in the Python stuff
> > > before we'd want to deprecate the scripted bundle.
> > >
> > > On the JRuby front, is that something you use actively? This question
> > > is for you and the entire community of course.
> > >
> > > Regards,
> > > Matt
> > >
> > > On Mon, Nov 6, 2023 at 7:12 AM Mike Thomsen 
> > > wrote:
> > > >
> > > > If we deprecate ExecuteScript, I think we need to have groovyx be
> ready
> > > to
> > > > function as a drop-in replacement if it's not there already.
> > > >
> > > > On Sun, Nov 5, 2023 at 9:21 PM Matt Burgess 
> > > wrote:
> > > >
> > > > > IIRC the removal of these engines was mostly due to lack of use or
> at
> > > > > least the perception thereof. If JRuby is being used by the
> community
> > > > > actively, I'm happy to revisit that discussion. Luaj's JSR-223
> > > > > interface left something to be desired, but JRuby just needed a
> > system
> > > > > variable set or something like that.
> > > > >
> > > > > For the groovyx bundle, because it is Groovy-specific I tend to
> think
> > > > > we could make better use of that than ExecuteScript, especially if
> we
> > > > > do get rid of all the engines. We have a Groovy-specific
> processor, a
> > > > > "real" Python SDK, and no more Nashorn. Perhaps we move all the
> > > > > scripted components to the Groovy bundle, although I believe some
> > > > > folks still make use of Jython for these. Of course if we reinstate
> > > > > JRuby for ExecuteScript it's probably best to keep things the way
> > they
> > > > > are, or create a jruby bundle. The original scripting bundle was
> > > > > aiming to support several engines, but if it turns out only one or
> > two
> > > > > will be useful, it may not be worth shoehorning all that JSR-223
> > logic
> > > > > when engine-specific components could be simpler, more easily
> > > > > maintained, and allow for the idioms of the language to be better
> > used
> > > > > (as is done in the groovyx bundle).
> > > > >
> > > > > Just my two cents, looking forward to everyone's thoughts!
> > > > >
> > > > > - Matt
> > > > >
> > > > > On Sun, Nov 5, 2023 at 8:31 PM Mike Thomsen <
> mikerthom...@gmail.com>
> > > > > wrote:
> > > > > >
> > > > > > https://issues.apache.org/jira/browse/NIFI-11646
> > > > > >
> > > > > > I get the removal of Lua, but not the removal of JRuby. It's a
> > clean
> > > > > > reimplementation of Ruby native to the 

Re: [VOTE] Release Apache NiFi 1.24.0 (RC2)

[Pierre Villard]

Killing this RC2 in light of the license/notice issue.
Will include a few additional commits in the RC3 that I'll start later
today or tomorrow.

Le mer. 15 nov. 2023 à 16:31, Pierre Villard 
a écrit :

> Team,
>
> I am pleased to be calling this vote for the source release of Apache NiFi
> 1.24.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.24.0
>
> The build artifacts are available on the Apache Nexus Repository:
>
> https://repository.apache.org/content/repositories/orgapachenifi-1239
>
> Git Tag: nifi-1.24.0-RC2
> Git Commit ID: b67f9add3f9cfe77146b8339c044f72f89684d51
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/b67f9add3f9cfe77146b8339c044f72f89684d51
>
> Checksums of nifi-1.24.0-source-release.zip
>
> SHA256: c9f8e493bf6b5eef8b53c8e96be5139f904e3187c89edb6b5b112ca3a172b6c5
> SHA512:
> 76859c5e8e888dc04604ee355bbe4e9050551bacecc68df8467ad0938cb2f1d7137211c98fb1793ab521556c6b7bf6899d97e754a33f0dafc109624125a5e46b
>
> 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: 272
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353443
>
> Release note highlights can be found on the project wiki:
>
>
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.24.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.24.0
> [] +0 no opinion
> [] -1 Do not release this package because...
>

Re: [CANCEL][VOTE] Release Apache NiFi 2.0.0-M1 (RC1)

[Dan S]

David,
 I would like to note one thing regarding the release notes. The following
tickets are listed

   - [NIFI-10792 ] -
   ConvertExcelToCSVProcessor : Failed to convert file over 10MB
   - [NIFI-12100 ] -
   Remove ConvertExcelToCSVProcessor


I don't think it makes sense to list NIFI-10792 since the
ConvertExcelToCSVProcessor
has been removed with NIFI-12100.

On Wed, Nov 15, 2023 at 3:06 PM David Handermann <
exceptionfact...@apache.org> wrote:

> Team,
>
> Thanks for the votes thus far.
>
> Unfortunately one of the new NAR files, nifi-shared-standard-nar did
> not include the required LICENSE and NOTICE files. This has been
> corrected in NIFI-12373 [1]. I am cancelling 2.0.0-M1 RC1 and will be
> preparing a new release candidate build soon.
>
> Regards,
> David Handermann
>
> [1] https://issues.apache.org/jira/browse/NIFI-12373
>
> On Wed, Nov 15, 2023 at 6:33 AM Csaba Bejan  wrote:
> >
> > +1 (binding)
> >
> > - Went through the helper guide and did a clean build
> > - Verified signatures and hashes
> > - Built on OSX 13.5.2
> > - Java version: Zulu21.28+85-CA (build 21+35)
> > - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
> >
> > - Started NiFi and created a simple flow
> > - Started MiNiFi and verified integration with C2 Server. Played around
> with the C2 protocol.
> >
> > Verified:
> > - NIFI-11514 MiNiFi Flow JSON support and deprecating YAML format.
> Migration tool from YAML to JSON
> > - NIFI-12333 MiNiFi property override through env and system variables
> > - NIFI-12335 Fix MiNiFi startup issue
> >
> > Thanks for RM'ing, David!
> >
> > Regards,
> > Csaba
> >
> > > On 2023. Nov 14., at 1:58, David Handermann <
> exceptionfact...@apache.org> wrote:
> > >
> > > Team,
> > >
> > > I am pleased to be calling this vote for the source release of Apache
> > > NiFi 2.0.0-M1.
> > >
> > > 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.0.0-M1
> > >
> > > The build artifacts are available on the Apache Nexus Repository:
> > >
> > > https://repository.apache.org/content/repositories/orgapachenifi-1236
> > >
> > > Git Tag: nifi-2.0.0-M1-RC1
> > > Git Commit ID: 0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> > > GitHub Commit Link:
> > >
> https://github.com/apache/nifi/commit/0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> > >
> > > Checksums of nifi-2.0.0-M1-source-release.zip
> > >
> > > SHA256:
> ba870d51e2362c2f07935634e30d469cb90cd71a65cc4ea205760a2192551696
> > > SHA512:
> bc25e1b1d27477950490e250297e74ec969b2ab1b351f318d0908e6c579e919972be5470acc9e147ea87a6185951c5c4f2d22d8f532eab0b045a2d7b922ad594
> > >
> > > 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: 934
> > >
> > >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599
> > >
> > > Release note highlights can be found on the project wiki:
> > >
> > >
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1
> > >
> > > 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.0.0-M1
> > > [] +0 no opinion
> > > [] -1 Do not release this package because...
> >
>

[CANCEL][VOTE] Release Apache NiFi 2.0.0-M1 (RC1)

[David Handermann]

Team,

Thanks for the votes thus far.

Unfortunately one of the new NAR files, nifi-shared-standard-nar did
not include the required LICENSE and NOTICE files. This has been
corrected in NIFI-12373 [1]. I am cancelling 2.0.0-M1 RC1 and will be
preparing a new release candidate build soon.

Regards,
David Handermann

[1] https://issues.apache.org/jira/browse/NIFI-12373

On Wed, Nov 15, 2023 at 6:33 AM Csaba Bejan  wrote:
>
> +1 (binding)
>
> - Went through the helper guide and did a clean build
> - Verified signatures and hashes
> - Built on OSX 13.5.2
> - Java version: Zulu21.28+85-CA (build 21+35)
> - Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)
>
> - Started NiFi and created a simple flow
> - Started MiNiFi and verified integration with C2 Server. Played around with 
> the C2 protocol.
>
> Verified:
> - NIFI-11514 MiNiFi Flow JSON support and deprecating YAML format. Migration 
> tool from YAML to JSON
> - NIFI-12333 MiNiFi property override through env and system variables
> - NIFI-12335 Fix MiNiFi startup issue
>
> Thanks for RM'ing, David!
>
> Regards,
> Csaba
>
> > On 2023. Nov 14., at 1:58, David Handermann  
> > wrote:
> >
> > Team,
> >
> > I am pleased to be calling this vote for the source release of Apache
> > NiFi 2.0.0-M1.
> >
> > 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.0.0-M1
> >
> > The build artifacts are available on the Apache Nexus Repository:
> >
> > https://repository.apache.org/content/repositories/orgapachenifi-1236
> >
> > Git Tag: nifi-2.0.0-M1-RC1
> > Git Commit ID: 0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> > GitHub Commit Link:
> > https://github.com/apache/nifi/commit/0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> >
> > Checksums of nifi-2.0.0-M1-source-release.zip
> >
> > SHA256: ba870d51e2362c2f07935634e30d469cb90cd71a65cc4ea205760a2192551696
> > SHA512: 
> > bc25e1b1d27477950490e250297e74ec969b2ab1b351f318d0908e6c579e919972be5470acc9e147ea87a6185951c5c4f2d22d8f532eab0b045a2d7b922ad594
> >
> > 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: 934
> >
> > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599
> >
> > Release note highlights can be found on the project wiki:
> >
> > https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1
> >
> > 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.0.0-M1
> > [] +0 no opinion
> > [] -1 Do not release this package because...
>

[VOTE] Release Apache NiFi 1.24.0 (RC2)

[Pierre Villard]

Team,

I am pleased to be calling this vote for the source release of Apache NiFi
1.24.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.24.0

The build artifacts are available on the Apache Nexus Repository:

https://repository.apache.org/content/repositories/orgapachenifi-1239

Git Tag: nifi-1.24.0-RC2
Git Commit ID: b67f9add3f9cfe77146b8339c044f72f89684d51
GitHub Commit Link:
https://github.com/apache/nifi/commit/b67f9add3f9cfe77146b8339c044f72f89684d51

Checksums of nifi-1.24.0-source-release.zip

SHA256: c9f8e493bf6b5eef8b53c8e96be5139f904e3187c89edb6b5b112ca3a172b6c5
SHA512:
76859c5e8e888dc04604ee355bbe4e9050551bacecc68df8467ad0938cb2f1d7137211c98fb1793ab521556c6b7bf6899d97e754a33f0dafc109624125a5e46b

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: 272

https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12353443

Release note highlights can be found on the project wiki:

https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version1.24.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.24.0
[] +0 no opinion
[] -1 Do not release this package because...

Re: [VOTE] Release Apache NiFi 2.0.0-M1 (RC1)

[Csaba Bejan]

+1 (binding)

- Went through the helper guide and did a clean build
- Verified signatures and hashes
- Built on OSX 13.5.2
- Java version: Zulu21.28+85-CA (build 21+35)
- Apache Maven 3.9.5 (57804ffe001d7215b5e7bcb531cf83df38f93546)

- Started NiFi and created a simple flow
- Started MiNiFi and verified integration with C2 Server. Played around with 
the C2 protocol.

Verified:
- NIFI-11514 MiNiFi Flow JSON support and deprecating YAML format. Migration 
tool from YAML to JSON
- NIFI-12333 MiNiFi property override through env and system variables
- NIFI-12335 Fix MiNiFi startup issue

Thanks for RM'ing, David!

Regards,
Csaba

> On 2023. Nov 14., at 1:58, David Handermann  
> wrote:
> 
> Team,
> 
> I am pleased to be calling this vote for the source release of Apache
> NiFi 2.0.0-M1.
> 
> 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.0.0-M1
> 
> The build artifacts are available on the Apache Nexus Repository:
> 
> https://repository.apache.org/content/repositories/orgapachenifi-1236
> 
> Git Tag: nifi-2.0.0-M1-RC1
> Git Commit ID: 0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> GitHub Commit Link:
> https://github.com/apache/nifi/commit/0a7ba3722001bb8c3f09755792c4db2b2ab61f36
> 
> Checksums of nifi-2.0.0-M1-source-release.zip
> 
> SHA256: ba870d51e2362c2f07935634e30d469cb90cd71a65cc4ea205760a2192551696
> SHA512: 
> bc25e1b1d27477950490e250297e74ec969b2ab1b351f318d0908e6c579e919972be5470acc9e147ea87a6185951c5c4f2d22d8f532eab0b045a2d7b922ad594
> 
> 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: 934
> 
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020=12339599
> 
> Release note highlights can be found on the project wiki:
> 
> https://cwiki.apache.org/confluence/display/NIFI/Release+Notes#ReleaseNotes-Version2.0.0-M1
> 
> 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.0.0-M1
> [] +0 no opinion
> [] -1 Do not release this package because...