5 ms·
Every 6 months, actually. In practical terms, unless you want to test out Java features (which can be removed with the next release), you only need to track th
by alphager 6y ago
Every 6 months, actually.
In practical terms, unless you want to test out Java features (which can be removed with the next release), you only need to track the LTS-releases every 3 years and actively upgrade every 6 years to stay on a supported version.
- leoh 6y agoThe average cadence, over the lifetime of Java, is actually something like a new version every 2.5 years. They have really ramped up.
- carimura 6y agoUp until 10, releases were feature-driven, meaning, based around the delivery of something when it was done like Generics in 5, Lambdas in 8, modularity system in 9, etc. With 10 and on, Java is now a time-based release cadence, every 6 months in September and March, like clockwork. What's ready goes in, what's not waits for the next train.
- leoh 6y agoI'm not sure this is ideal for users, no? Each time something is deprecated (e.g. nashorn in JDK15), I have to go check the long term support schedule, etc. And I have to imagine it's much harder to maintain, creating the potential for patchwork fixes across various JDKs.