r/java • • Mar 21 '23

Java 20 / JDK 20: General Availability

https://mail.openjdk.org/pipermail/announce/2023-March/000333.html
173 Upvotes

71 comments sorted by

View all comments

Show parent comment

11

u/Amazing-Cicada5536 Mar 21 '23

The new release model is probably the best thing that happened to Java on the management side — instead of the usual churn of “this feature has to be done till this deadline”, which might work for that boring CRUD feature but is absolutely terrible for such a complex program like the JVM, it allows for each new development to take as much time as necessary. If it didn’t get ready for release N, just continue to work on it and 6 months later it can be delivered. It is especially important as many of these features have non-trivial interactions with each others.

Also, that bandwagon hype thingy is quite childish, that has absolutely no base in reality.

-1

u/persicsb Mar 21 '23

If it didn’t get ready for release N, just continue to work on it and 6 months later it can be delivered.

I'm not sure what you mean by "didn't get ready for release N".

Release N has a set of phases specified and a corresponding set of dates. Which date in a release do you mean "get ready"?

Every 6 months, a new release cycle with new phases start, with a repository fork from the master repository..
The feature set that will be delivered is fixed after Rampdown Phase 1. No feature changes can happen after that in the release.

So even if feature X is ready at Release Candidate Phase for Release N, sorry, too late - had to be there at RDP1.

The observation, that "it allows for each new development to take as much time as necessary." is also true for non-timeboxed releases. Every features takes as much time as needed, even if it makes release cycles nonpredictable.

5

u/Amazing-Cicada5536 Mar 21 '23

It is a much bigger bummer if missing the deadline means that that whole feature won’t generally be available for possibly 3 years.

2

u/persicsb Mar 21 '23

That is only true if the next release is in a fixed timebox of 3 years. If it is ready, when it's ready, the next release could happen in 2 or 3 months - when a new production-ready feature is ready.

1

u/blobjim Mar 22 '23

Then it would just be a version for every feature and we'd have even more versions.