Question
Why did IntelliJ IDEA stop doing the frequent EAP blog posts?
Some users complain that those posts were tempting enough for them to try out an EAP. And now they are staying on a stable version more as they don't really know what's in the EAP.
Answer
Starting with the 2025.2 cycle we intentionally moved away from weekly "what's new in this EAP build" blog posts to avoid spamming the blog with small, incremental changes and instead focus on a few more substantial updates per release. The EAP itself is still very much alive, just the communication format changed.
For a while, the flow looked roughly like this:
-
An opening EAP blog post was created per major version (e.g., IntelliJ IDEA 2025.3 Early Access Program Is Open!) that outlined the main themes and directions for the cycle.
-
A Beta / EAP closure post was added (like the IntelliJ IDEA 2025.2 Beta: EAP Closure and Our New Approach to Release Updates post) explaining the new communication approach and summarizing the most important changes.
-
For the final release, a focused "What's New" page (example for 2025.3) plus a "What's Fixed" blog post were made that highlight key features and major quality improvements, with the full list of changes still available in the release notes and summarized in posts like the IntelliJ IDEA 2025.3 Release Candidate Is Here.
Starting with 2026.1 we are:
-
Deciding for each EAP release separately on whether it needs an EAP opening blog post, depending on how many new features it contains or how important the features are.
-
Discontinuing Beta/EAP Closure posts with a 90% chance.
If you want a single place to see what's in each build, there's also a "Latest Builds and Release Notes" page for IntelliJ IDEA that always points to the current EAP / Beta / RC build and its detailed notes.
Comments
0 comments
Please sign in to leave a comment.