Re: [jakarta.ee-spec.committee] Follow up on the topic of Jakarta EE 11

[Scott Stark <sstark@xxxxxxxxxx>]

Maybe another way to lessen the impact of any change would be to
separate the ratification of a specification via a compatible
implementation that runs under different Java SE versions such that
vendors backing a particular compatible implementation for their
product choose what works for them. A vendor that wants to certify
under Java SE 17 would have the burden of producing the ratifying
compatible implementation if the initial version was Java SE 21. We
are using the Concurro project in WidFly/EAP, so we would be willing
to produce the Java SE 17 ratifying compatible implementation of that
project. We will take on work that benefits our users.

On Sun, Jan 28, 2024 at 10:27 AM Scott Stark <sstark@xxxxxxxxxx> wrote:
>
> There are plans for an 8.x supporting EE 11 in 2025.
>
> On Sat, Jan 27, 2024 at 8:40 AM Arjan Tijms <arjan.tijms@xxxxxxxxxxx> wrote:
> >
> > Hi,
> >
> > On Sat, 27 Jan 2024 at 03:02, Scott Stark via jakarta.ee-spec.committee <jakarta.ee-spec.committee@xxxxxxxxxxx> wrote:
> >>
> >> Correct, we cannot drop support for Java SE 17 in the timeframe EE 11
> >> will be incorporated into EAP 8.x.
> >
> >
> > Correct me if I'm wrong, but isn't EAP 8.0 supposed to be supporting Jakarta EE 10 and still not released?
> >
> > See https://access.redhat.com/articles/113373
> >
> > Wouldn't an EAP 8.x or 9 supporting EE 11 be realistically targeted for around 2026/2027?
> >
> > Kind regards,
> > Arjan Tijms
> >
> >