This shouldn’t come as a surprise since some APIs have been deprecated for ages and have been superseded by newer APIs. While some APIs are as good as gone, others are eligible for removal in a future release but they haven’t been removed from this Specification.
JDK 10’s Rampdown Phase Two ran until February 8, which means there’s just the Release Candidate phase standing between us and the next Java version. Speaking of, the first JDK Release Candidate is here.
With only six months between releases, can anybody be surprised that a new Java version will consist entirely of small-bore incremental improvements? And when it does, can anybody be surprised when nobody seems particularly excited by it? Here, Wayne Citrin talks about the emerging problem of release fatigue.
There is a significant amount of work going into JDK10 to support containerized JVMs. In this post, Oracle’s Matthew Gilliard will show how the next release of the JDK will be container-aware.
It’s official. The next Java version will be called JDK 10. Now that everything is clear, Rampdown Phase One can begin. These are the features that made the cut.
It’s official. The next Java version will be called JDK 10. It’s time to say goodbye to the scheme introduced by JEP 223 since it’s no longer “well-suited to the [six-month cadence] future”.
Two weeks ago, Mark Reinhold offered three alternatives for the new version-numbering scheme. Now it’s time to present the specific proposal. In short, “JDK 10 is a feature release, JDK 10.0.1 and 10.0.2 are update releases with compatible bug fixes, and there is no interim JDK 10.1 release since in this model the next opportunity to add features is JDK 11.”