The Jakarta EE 9 Release Plan is now available!
In late 2019, it was reviewed and endorsed by the Platform Project, as well as the Jakarta EE Steering Committee.
In early 2020, an official ballot was approved by the Jakarta EE Specification Committee.
A Jakarta EE 9 Release Plan FAQ has also been created to help clarify aspects of the Release Plan.
The key goal of the Jakarta EE 9 Release Plan is to move from the javax namespace to the jakarta namespace.
Almost all of the Jakarta EE 9 components will be exclusively focused on that effort.
But, there are a few components (ie. EJB, Activation, maybe others..) that need additional changes to their APIs in the Jakarta EE 9 timeframe.
For these components, a separate Release Plan will be necessary to outline the reasoning for these additional updates.
Also, it is expected that these type of changes will still be required to stick to the date goals being set for Jakarta EE 9.
These component release plans are not as elaborate as the Jakarta EE 9 Release Plan. They should reference this overall Release Plan as a basis for the individual component release plan. These component release plans will utilize the existing Eclipse mechanism for defining an upcoming release, which is documented in the Eclipse Foundation Project Handbook.
Overall schedule (dates are tentative and subject to change). The wave content is based off of the descriptions in the Jakarta EE 9 Release Plan.
Final Jakarta EE 9 release (Java 8) - Nov 20 completion (proposed)
Note: We are now driving towards a Friday, Nov 20 date for Jakarta EE 9 completion. Jakarta EE 9 will be formally announced at the JakartaOne Livestream on Tuesday, Dec 08.
Jakarta EE 9 will track its development progress with a Github Project Board. An individual Epic Issue was created for each Specification Project to track its progress. For example, here’s a link to the Jakarta EE Platform Specification Version 9 Issue.
The Jakarta EE Release repo will also be used for Issue tracking across the overall project. For example, the Milestone/Release Candidate API artifacts are tracked in this repository.