Four LTS Java Versions Get End-of-Support in a Three-Year Window (2029-2032)

Source: Slashdot

Simon Ritter joined Sun Microsystems in 1996 and spent time working in both Java development and consultancy. He’s now written an opinion piece for InfoWorld warning that “Between 2029 and 2032, every currently supported long-term support (LTS) version of Java will reach end-of-support within a single three-year window.”

That’s Java 17 in 2029, Java 8 in 2030, Java 21 in 2031, and Java 11 in 2032…

On paper, this looks like a manageable upgrade cycle. In practice, it creates a collision of timelines that most enterprises have failed to forecast. Organizations attempting to modernize incrementally — moving application by application, version by version — are operating on a model that the calendar has already rendered obsolete… [W]hen every major Java version expires in the same compressed window, sequential planning collapses. By the time this becomes obvious, organizations will be forced into reactive mode, making rushed decisions under extreme pressure.

For organizations planning traditional stepwise upgrades — Java 8 to Java 11 to Java 17 to Java 21 — this convergence elevates a routine maintenance task into a structural crisis. Enterprises with large Java estates will be forced to upgrade multiple applications across multiple versions simultaneously to maintain security compliance and business continuity.

“Parallel modernization requires parallel capacity — something most organizations haven’t budgeted for,” he points out. “This explains why traditional approaches struggle to scale.”