Thanks Matt and Peter!

On Mon, Nov 4, 2024 at 12:15 PM Peter Turcsanyi <turcsa...@apache.org>
wrote:

> Continuing the work on the Salesforce upgrade, PR [1] created for the 3.x
> => 4.x change.
>
> Regards,
> Peter
>
> [1] https://github.com/apache/nifi/pull/9484
>
> On Mon, Oct 28, 2024 at 9:07 PM Matt Burgess <mattyb...@apache.org> wrote:
>
> > For Redis I wrote up [1] and put up a PR [2] in case we do agree to
> upgrade
> > to the latest version. I tested all Redis-backed components with no
> errors
> > or changes in behavior
> >
> > Regards,
> > Matt
> >
> > [1] https://issues.apache.org/jira/browse/NIFI-13944
> > [2] https://github.com/apache/nifi/pull/9465
> >
> >
> > On Mon, Oct 28, 2024 at 3:13 PM Matt Burgess <mattyb...@apache.org>
> wrote:
> >
> > > I added [1] and a PR [2] to upgrade the easy ones. I commented on the
> > > Salesforce version and we should decide if we want to update the Mongo
> > > components to 8, and redis to 6.4+
> > >
> > > Regards,
> > > Matt
> > >
> > > [1] https://issues.apache.org/jira/browse/NIFI-13943
> > > [2] https://github.com/apache/nifi/pull/9464
> > >
> > > On Mon, Oct 28, 2024 at 1:36 PM Joe Witt <joew...@apache.org> wrote:
> > >
> > >> Team,
> > >>
> > >> These need help from maintainers to keep them updated or they risk
> > >> requiring removal.
> > >>
> > >> Problematically Dated libraries we have shown as:
> > >> package-name currVersion latestVersionAvail
> > >>
> > >> com.dropbox.core 5.4.6 7.0.0
> > >>  One year old
> > >>
> > >> org.apache.camel/salesforce 3.14.10 4.8.1
> > >>  Already EOL for two years.
> > >>
> > >> org.mongodb 4.11.4 5.2.0
> > >>    Compatible with Mongo 6 and 7 which are still supported. (all older
> > are
> > >> EOL)
> > >>    Not compatible with Mongo 8 which is latest.
> > >>
> > >> org.questdb 7.4.2 8.1.4
> > >>
> > >> org.snmp4j 2.8.18 3.8.2
> > >>
> > >> redis.clients 3.10.0 5.2.0
> > >>  Compatible with up to 6.2 which is EOL on Feb 2025
> > >>  Not compatible with 6.4 or 7.x which are latest
> > >>
> > >> Thanks
> > >> Joe
> > >>
> > >
> >
>

Reply via email to