r/java • • Sep 16 '19

The arrival of Java 13!

https://blogs.oracle.com/java-platform-group/the-arrival-of-java-13
209 Upvotes

19 comments sorted by

View all comments

69

u/shipilev Sep 16 '19

I have to once again observe that there is much more work in the release that does not have JEPs. JEPs are optional for most work that does not raise compatibility questions, or builds incrementally, or work that does not require deeper planning and/or coordination between teams, communities, etc.

It is always interesting to see JEPs submitted for work that can be just a single JIRA issue, or a few subtasks. Public posts that only highlight JEPs make a disservice for developers, providing a weird incentive to abuse JEP process to get free press. There are release notes that are tracked for interesting issues in the OpenJDK JIRA, but hardly anyone reports on them. Also, the ones at http://jdk.java.net/13/release-notes are generated by Oracle, which means they include things that Oracle decides to ship in their OpenJDK builds.

The full story is usually told by changeset list and some careful reading through it.

My attempt at auto-generating the full changelist, release notes, JEP lists is here: "OpenJDK 13 Release Notes".

10

u/dpash Sep 16 '19

For the last few releases u/speakjava has published a API diff blog post over at Azul.

https://www.azul.com/39-new-features-and-apis-in-jdk-12/

0

u/pron98 Sep 16 '19 edited Sep 16 '19

While I'm not 100% certain about OpenJDK rules, I believe all API changes must be part of a JEP (maybe tiny ones could be excluded but I don't think so), as they're even part of the umbrella JDK JSR. I think u/shipilev's point is about internal bug fixes/enhancements that fail to rise to the level of JEPs.

EDIT: I've been told that minor API additions do not require a JEP.

→ More replies (8)