Create Release Plan for Tags for Jakarta EE 12

[jhanders34]

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

• Link to release plan for your component: https://projects.eclipse.org/projects/ee4j.jstl/releases/3.1.0
• Link to release plan review PR in the specifications repository: Jakarta Standard Tag Library 3.1.0 plan review specifications#824

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.

[pnicolucci]

DRAFT

I've been working to review the current issues in the Jakarta Tags GitHub repo with @volosied to determine what could be done for Jakarta EE12.

I plan to keep this issue updated with ideas and then send a note to the Jakarta Tags mailing list for additional community feedback.

Plan:

• Implement new feature: Support java.time API in <fmt:parseDate> and <fmt:formatDate>
• Review any other enhancement requests and determine if they can be completed within EE12.
• Finalize the TCK move to the Jakarta Tags repo and remove it from the platform: tck is using org.eclipse.ee4j as groupId #270
• Review issues and resolve existing bugs / provide spec clarification if any is necessary, as time permits for Jakarta EE12
• Use the following query to track issues targeted for Jakarta EE12: https://github.com/jakartaee/tags/issues?q=is%3Aissue%20state%3Aopen%20label%3AJakartaEE12

Jakarta Tags has very few committers so we don't want to bite off more than we can deliver.

Major or Minor release?
Given we're currently only adding additional support to existing tags and doing a cleanup, I don't see why we couldn't do a 3.1 minor release rather than a 4.0 release. We should update to the minimum Java version defined by Jakarta EE 12 of Java 21.