Hi JB and Chris.

My concern about doing so is that it may create false expectations for
users and add more burden to the maintainers. On the webpage
https://activemq.apache.org/components/classic/download/ , it states that "
*Deprecated*: Reached end-of-life and is no longer maintained. Deprecated
versions do not receive updates." If we provide an exception for a
functional fix , those users on 5.16.x may never migrate because they know
an exception is possible. Is there something else (like a blog post on
migration) we can do to help those Java 8 community users without releasing
updates to 5.16 and 5.17?

Thanks,
Ken

On Thu, Feb 27, 2025 at 3:11 PM Christopher Shannon <
christopher.l.shan...@gmail.com> wrote:

> Hi JB,
>
> Sounds good, I agree that if we are doing the releases we should also back
> port a couple of the other important fixes as well.
>
> Chris
>
> On Thu, Feb 27, 2025 at 3:27 PM Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
>
> > It’s a good point. I see a couple of important fixes that would be good
> to
> > have in 5.16.8 / 5.17.7.
> >
> > We are not supposed to actively maintain these branches. But it’s a fair
> > request for our jdk8 users still.
> >
> > I don’t see problem to do new releases on these branches for important
> > fixes.
> >
> > Regards
> > JB
> >
> > Le jeu. 27 févr. 2025 à 14:24, Christopher Shannon <
> > christopher.l.shan...@gmail.com> a écrit :
> >
> > > That should have said "backported the important exception translation
> > bug"
> > >
> > > On Thu, Feb 27, 2025 at 8:23 AM Christopher Shannon <
> > > christopher.l.shan...@gmail.com> wrote:
> > >
> > > > I just noticed that we never released version 5.16.8 or 5.17.7 and
> both
> > > of
> > > > those releases have backported the import exception translation bug
> fix
> > > > from https://issues.apache.org/jira/browse/AMQ-9418
> > > >
> > > > I think these are important to release, especially 5.16.8, because
> it's
> > > > the last JDK 8 compatible version.
> > > >
> > > > Thoughts?
> > > >
> > > > Chris
> > > >
> > >
> >
>

Reply via email to