Thanks for initiating the discussion! I agree that moving toward the next release, incorporating these several NiFi API updates, sounds good.
Regards, David Handermann On Tue, Jul 8, 2025 at 3:42 PM Matt Burgess <mattyb...@apache.org> wrote: > > I'd like to get [1] in if possible so I can start working on the > implementations in the NiFi codebase. Not a blocker of course, just a wish > :) > > Thank you, > Matt > > [1] https://issues.apache.org/jira/browse/NIFI-14571 > > On Tue, Jul 8, 2025 at 9:28 AM Pierre Villard <pierre.villard...@gmail.com> > wrote: > > > Team, > > > > I have recently submitted a NIP [1] for a small change in the NiFi > > API. Assuming the corresponding PR [2] is approved and merged, I'd > > like to see a release of NiFi API 2.2.0 happen and I'm happy to take > > care of the release duties. > > > > Once this is done, it would be a great time to make the appropriate > > changes in NiFi to reference the updated API version and make the > > appropriate changes mentioned in the NIP (I have a PR ready for that), > > to then release NiFi 2.5.0. > > > > We have over 130 JIRA issues resolved [3] so it's definitely time to > > have a new release anyway. I'm also happy to handle RM duties for the > > release. > > > > Let me know if there are specific PRs being actively reviewed that > > should be considered as a blocker before starting the process. > > > > Thanks, > > Pierre > > > > [1] https://issues.apache.org/jira/browse/NIP-8 > > [2] https://github.com/apache/nifi-api/pull/8 > > [3] https://issues.apache.org/jira/projects/NIFI/versions/12355903 > >
