Confused about the release cycles of OpenJDK and OpenJFX and the relationship between them? Read on!
Since 2018, Java switched to a 6-months release cycle. Every new release brings new finished features, but also "preview" ones which are not finished yet. These can be enabled with a flag (`
java --enable-preview`) to allow developers to start experimenting with them and provide feedback to the developers to further improve these so they can become available in one of the next releases.
Thanks to this fixed schedule, new versions are no longer causing major changes, but provide a steady, predictable, and stable flow of new features.
If you're in doubt if you should move to a newer JDK version, make sure to read "Modern Java toys that boost productivity, from type inference to text blocks. Developers using older versions of the Java platform are missing out." by Angie Jones on the Oracle Java Magazine.
In the past, JavaFX has been bundled with the Oracle JDK (until JDK 11), but it was always a project on its own as openjfx.io, with its sources on GitHub. Gluon builds and distributes the OpenJFX releases, following the same 6-month release cycle.
An overview of all the changes in OpenJFX since version 11 are available here.
Relationship Between OpenJDK and OpenJFX Releases
Until now, the OpenJFX releases did not require a specific OpenJDK version. This means you can use OpenJDK 11 combined with OpenJFX 15.
At this moment, there are no planned features or changes in OpenJFX which require new JDK features (text blocks, records, etc), so the next releases of OpenJFX will most probably still be compatible with JDK 11.
Yes, OpenJDK and OpenJFX are aligned in the number of releases per year (2x) and follow the same major version numbering (15, next one will be 16).
No, they are not "bound together" and follow their own path.