Pierre,

Thanks for picking this up, I agree with getting a release candidate
going soon. I will look at the Kafka bug issue. The Local Changes
improvement looks useful, although I would not hold on that if
everything else is ready.

Regards,
David Handermann

On Tue, Feb 3, 2026 at 11:32 AM Pierre Villard
<[email protected]> wrote:
>
> Team,
>
> I think we should get a 2.8.0 release candidate going forward as we
> have a few users being hit by the known issue around Azure components.
> I am happy to take care of the release duties.
>
> Are there some PRs that we believe should be absolutely included?
> From my point of view the Kafka bug fix [1] and the Show Local Changes
> improvement [2] are two PRs that would be good to have since both have
> been reported by the community.
>
> Some additional ones would be nice-to-have but not blockers.
>
> Thanks,
> Pierre
>
> [1] https://github.com/apache/nifi/pull/10769
> [2] https://github.com/apache/nifi/pull/10681
>
> Le mer. 21 janv. 2026 à 08:53, Fabian Reiber <[email protected]> a écrit :
> >
> > Hi,
> >
> > thanks for your work and your offer for comments.
> >
> > It would be nice to get the fix for issue [NIFI-15464] in the new 2.8.0
> > release :)
> >
> > Best Regards
> > Fabian Reiber
> >
> > [NIFI-15464] https://issues.apache.org/jira/browse/NIFI-15464
> >
> > On 1/20/26 5:33 PM, Kevin Doran wrote:
> > > Thanks, Pierre. Sounds good to me.
> > >
> > > On Tue, Jan 20, 2026 at 11:00 AM Joe Witt <[email protected]> wrote:
> > >> Very nice!  Look forward to the vote.
> > >>
> > >> On Tue, Jan 20, 2026 at 8:59 AM David Handermann <
> > >> [email protected]> wrote:
> > >>
> > >>> Pierre,
> > >>>
> > >>> Thanks for initiating this discussion, I agree that the NiFi API is in
> > >>> a good place for another minor release, setting the foundation for a
> > >>> NiFi 2.8.0 release version. There has been a lot of progress on the
> > >>> development branches for the Connector work, but it makes sense to
> > >>> continue with these incremental releases before any of those changes
> > >>> have landed.
> > >>>
> > >>> Regards,
> > >>> David Handermann
> > >>>
> > >>> On Tue, Jan 20, 2026 at 9:38 AM Pierre Villard
> > >>> <[email protected]> wrote:
> > >>>> Team,
> > >>>>
> > >>>> We merged a few changes for the NiFi API (parameter tags, properties
> > >>>> migration for registry clients and parameter providers, and recording
> > >>>> gauges). I will proceed with a release candidate for the NiFi API
> > >>>> later today.
> > >>>>
> > >>>> Once released, I think we should quickly follow-up with a NiFi 2.8.0
> > >>>> release to include the NiFi API version change but also to release a
> > >>>> few important bug fixes (already 110+ issues with NiFi 2.8.0). However
> > >>>> there are some PRs that we likely want to get merged before preparing
> > >>>> the release candidate. Feel free to comment in this thread if some
> > >>>> specific PRs should have special attention for this release.
> > >>>>
> > >>>> Thanks,
> > >>>> Pierre
> >
> > --
> > Fabian Reiber, M.Sc.                      (Entwicklung interner Software)
> > Phone: +49 40 808077-555 Fax: +49 40 808077-556 Mail: [email protected]
> >
> > DFN-CERT Services GmbH, https://www.dfn-cert.de/, Phone  +49 40 808077-555
> > Sitz/Register:  Hamburg,  AG Hamburg,  HRB 88805,  Ust-IdNr.: DE 232129737
> > Nagelsweg 41,  20097 Hamburg,  Germany.   CEO: Dr. Klaus-Peter Kossakowski
> >
> >

Reply via email to