In June and December, we fork
the main line into a stabilization repository [1]. Changes are backported
from the jdk repository into the stabilization repository, typically by the
Committer who contributed the change [2]. The stabilization repository is
archived when the release is delivered.

We inherited the convention of forking repositories from Mercurial, which
originally had weak support for branches.

Time to check in with where were are with String Templates. We’ve gone through two rounds of preview, and have received some feedback.

Specifically, the role of processors is “outsized” to the value they offer, and, after further exploration, we now believe it is possible to achieve the goals of the feature without an explicit “processor” abstraction at all! This is very positive development

Testing asynchronous systems is hard. Not only does it require handling threads, timeouts and concurrency issues, but the intent of the test code can be obscured by all these details. Awaitility is a DSL that allows you to express expectations of an asynchronous system in a concise and easy to read manner

Up to JDK 22, this feature is enabled by default, which may have been reasonable when it was introduced in JDK 6 circa 2006, but from a current perspective, in the interest of making build output more robust against annotation processors being placed on the class path unintentionally, this is much less reasonable. Hence, starting with JDK 23, javac requires an additional command-line option to enable annotation processing.

Is Java heavyweight? will the container images be huge? Nope, Java is pretty good at producing decent size container images. The table below shows the container image sizes for a variety of popular open source project. Java does pretty well on these measures.

This release improves error and warning reporting for variant issues during dependency resolution. It also exposes structural details of Java compilation errors for IDE integrators, making it easier to analyze and resolve issues.