For planning purposes, recall that projects must start their version release with a Specification Plan Review Ballot. This is facilitated by and voted on by members of the Jakarta EE Specification Committee. This plan should include
For your planning, you should provide a schedule that shows the two-week Specification Release Ballot prior to the <mumble-mumble> milestone proposed on the EE 11 planning page. As part of the Specification Plan Ballot, a new “work-in-progress” page will be created for this specification version at https://jakarta.ee/specifications/<your-API-short-name>/<proposed-relese-number>. Once the specification release review ballot is concluded this page will be promoted to final status and will include all the artifacts and materials needed by each completed Specification Version. You may contact the Jakarta EE Specification List for assistance and/or questions regarding the ballot process and requirements.For project artifact release tracking each project is also required to create a Release Record using their project tracking PMI page tools located at https://projects.eclipse.org/projects/ee4j.<your-specification-name>. This release record will contain a similar abstract as included on the specification pages. This release record triggers the release review processes that are carried out by the Eclipse PMO for license, dependency management, and legal review. You may contact the Jakarta EE PMC mailing list for assistance and questions.
More details can be found at