Re: [faces-dev] Faces 5.0 release plan

[Arjan Tijms <arjan.tijms@xxxxxxxxxxx>]

Hi,

Yes, splitting API from IMPL has zero benefits for any user. This is, I think, why it suffered from the "starvation effect"; which is an issue that must be done, but because it's consistently at a low priority doesn't ever actually get done.

So at some point, you just have to do it, even though it's not the highest priority. But I'll take this one up. I've been working on similar-ish splits throughout the EE4J/Jakarta codebase.

Btw, we can still do a 4.1 with some small changes. There was already a proposal for that. 5.0 is just the big plan for EE 11 in mid 2024.

Kind regards,

Arjan Tijms

On Fri, 24 Feb 2023 at 17:22, Thomas Andraschko <tandraschko@xxxxxxxxxx> wrote:

also, tbh, there are so many important tickets for users - whereas real splitting API from IMPL doesnt bring any benefit for users, i would not invest to much time here for now.

You know, MyFaces contains many implementation specific code, too.

Am Fr., 24. Feb. 2023 um 17:20 Uhr schrieb Thomas Andraschko <tandraschko@xxxxxxxxxx>:

so the next version is 5.0, not 4.1?

what are plans? i already set some some milestones for ticket, i would like to see

Am Fr., 24. Feb. 2023 um 17:11 Uhr schrieb Arjan Tijms <arjan.tijms@xxxxxxxxxxx>:

Hi,

I started with the release plan for Faces 5.0.

See here: https://projects.eclipse.org/projects/ee4j.faces/releases/5.0/plan

Kind regards,

Arjan Tijms

_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev

_______________________________________________
faces-dev mailing list
faces-dev@xxxxxxxxxxx
To unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/faces-dev