Create Release Plan for Faces for Jakarta EE 12

[jhanders34]

Follow the release plan process in the Jakarta Specification process guide to create a release plan for Jakarta Faces for inclusion in Jakarta EE 12.

• Link to release plan for your component: https://projects.eclipse.org/projects/ee4j.faces/releases/5.0
• Link to release plan review PR in the specifications repository: Jakarta Faces 5.0 Plan Review specifications#801

Things to include in the release plan are (but not limited to):

• New features
• Deprecation of existing function (which may be replaced with new function)
• Removal of previously deprecated function (requires a major version update)
• Other backward incompatible changes besides removal of deprecated function (requires major version update)
• Added or removed dependencies
• Notable newer Java SE features used
• New TCK tests for existing function that was not tested enough or tested at all
• Moving TCK from platform TCK to platform-tck repository to component repository
• Minimum Java SE version update (For Jakarta EE 12, the platform committee has declared that Java SE 21 will be the minimum Java SE level. As such I believe most release plans should state the same minimum Java SE level of 21.)

For each item in your release plan, there should be an issue opened in your repository and it should have the label EE12.

Resources to review for ideas of what to include in your release plan are this GitHub query that includes Jakarta platform issues that are labeled EE12, this google doc that is tracking ideas for Jakarta EE 12 content, and existing issues in your component's GitHub repository.

If your component does not plan to have a new release for inclusion in Jakarta EE 12 and just plans to use an existing release, close out this issue with that information. Do note that if your component is referenced in jakartaee/platform#1018, you should be planning to have a minor release at minimum. It may only contain the changes to remove references to SecurityManager / AccessController.

[arjantijms]

The list of issues targeting Jakarta EE 12 / Faces 5.0

https://github.com/jakartaee/faces/issues?q=is%3Aissue%20milestone%3A5.0%20sort%3Acreated-asc

[arjantijms]

Draft plan: jakartaee/specifications#801

@BalusC @tandraschko let me know what you think about it.

[tandraschko]

whats the planned release date?
if its soon, we need to retarget some of the issues, no impl handled yet

[BalusC]

I think it's ok ..

Does it mean we need to hold on all 5.0 work??

[jhanders34]

As said in the PR, the template used for the description isn't the release plan review one.

[jhanders34]

whats the planned release date? if its soon, we need to retarget some of the issues, no impl handled yet

This isn't a release review, but a plan review. You can specify when you believe you can be complete. In general the Jakarta EE 12 plan is to ship in first half of 2026. Likely we will want to have component specs complete by end of year. We will want to have implementations tested on both Java 21 and 25. Java 25 will release in September of this year.

[BalusC]

Ah ok I guess we can reset 5.0 target date to 1 september.

[mnriem]

@BalusC if we make sure we run TCK along side while developing new features could we do target of December 1st instead?

[BalusC]

I always run (new) TCK.

Not sure on "old TCK". It doesn't seem to work at my machine and also seems to be disabled in Eclipse CI for 4.1 (but is enabled in 4.0 hence it takes ~4h instead of 1).

@arjantijms do you know more on this?