Welcome to issue number three hundred and twenty-nine of Hashtag Jakarta EE!

The upcoming week, I will be in Brussels for Open Community eXperience 2026. My talk, titled The Past, Present, and Future of Enterprise Java – with Jakarta EE is scheduled for Wednesday. When I am not attending other talks or roaming the hallway, I can be found staffing the Eclipse Foundation booth in the exhibition area. I hope to see you there!

The release of Jakarta EE 12 consists of multiple Milestones that are continuously being refined to reflect the current status. In the Platform call last week, the platform project set up expectations for a couple of the milestones. First out is Milestone 4, in which the specifications that are part of Jakarta EE Core Profile are expected to show progress in the form of milestone or beta-releases.

M4 Apr 1 to May 15
– REST 5.0 M1 API / spec
– CDI 5.0 Milestone / Beta (currently at Alpha4)
– JSON-P 2.2 M1 API / spec
– JSON-B 3.1 M1 API / spec
M5 May 16 to Jun 30
– content to be defined
M6 Jul 1 to Aug 15
– content to be defined
M7 Aug 15 to Sep 30
– Ideally, we release Core profile here or soon after
M8 Oct 1 to Nov 15
– content to be defined
M9 Jan 1 to Feb 15, 2027
– Finalize all other specifications
M10 Feb 16 to Mar 31, 2027
– Release Platform TCK with ratifying impl

The Platform Project will continue to refine this timeline by adding expectations to each milestone. Note that even if a specification is not listed for a specific milestone, nothing prevents it from publishing ahead of time. If the current plan holds, we should be able to release Jakarta EE Core Profile in Q4, 2026, while Jakarta EE Web Profile and Jakarta EE Platform will be released in Q1 or Q2 next year. This follows the same pattern as for Jakarta EE 11.