Welcome to issue number three hundred and eighteen of Hashtag Jakarta EE!
As I write this, I am in Brussels for FOSDEM’26. Stay tuned for an update from this conference in a separate post shortly. Fun fact is that I am sitting in exactly the same place in the lobby of the same hotel I stayed at for FOSDEM’19 writing this post as I did for Hashtag Jakarta EE #5. I think that it was in that moment that I realised that this would be a weekly blog series.
After FOSDEM, I am headed directly to Stockholm for Jfokus 2026. Whenever I am at Jfokus, I am hosting the Jfokus 2026 Morning Run, and this year is no exception. There is no need to sign up for it. Just show up outside the venue at 7:15 on Wednesday morning.
From the discussions in the Jakarta EE Platform call the last couple of weeks, it looks like we won’t see a release of Jakarta EE 12 on this side of summer (on the Northern Hemisphere at least). The reason is that since Jakarta EE 11 was delayed by a year, most of the vendors are currently working on their implementations. Which does not leave much resources to work on the Jakarta EE 12 specifications. At the same time, we want to play catch-up with the original plan and direction directive from the Steering Committee of the Jakarta EE Working Group to release a major release of Jakarta EE 12 about six to nine months after an LTS release of Java. So a compromise will be to release Jakarta EE 12 by the end of the 2026. The deliberations are still going on, so stay tuned on more updates.
The registration for Open Community Experience 2026 has opened. I will be presenting The Past, Present, and Future of Enterprise Java at the main stage there.
