Community members, Executive Summary 1. See issue #671. a. If you don't plan to have a new version for your specification in EE 12, just close the issue. b. If you plan to have a new version, use
the issue to create a release plan by April 15,
Community members,
a. If you don't plan to have a new version for your specification in EE 12, just close the issue.
b. If you plan to have a new version, use the issue to create a release plan by April 15, 2025.
2. See
this dashboard where the component release plan issues are tracked.
On Monday I opened
issue #671 in your repository to request your community to consider a new release of your component for Jakarta EE 12 by creating a new release plan. The issue contains a lot of details that explain what to do to create a release plan. You can use the
issue to document initial thoughts and reference other issues in your repository as you work out what you want to include in a release plan.
A dashboard in GitHub was created to track the status of the release plan issues. The dashboard, located
here, contains both a Board and Table view of the release plan issues. What is being asked of each community is to decide on if you plan to have a new release to be considered for EE 12 or not. If not, closing the issue will move it to the final column
on the dashboard. If you are planning to have a new version of your component for EE 12, please follow the instructions in the issue by April 15, 2025 in order to get your issue moved to the second column for your mentor to look at the issue and get it ready
for a plan ballot. You will see that your issue in the board includes the name of the mentor that was assigned to your component in EE 11.
Jared Anderson and Ed Burns
Jakarta EE 12 Release Co-coordinators
