Java 29 LTS in September 2027: plan the jump from Java 21 or 25

Java 29 is the next planned LTS, due September 2027. Teams on 21 should move to 25 now; teams on 25 can plan 29 for 2028.

Read time
15 min
Word count
2.3K
Sections
9
FAQs
8
Share
Software architect reviewing a staged Java LTS upgrade plan, beside a Java 29 LTS title and Java, Oracle and OpenJDK logos
On this page · 9 sections
  1. What is confirmed about Java 29, and what is not
  2. Support dates you are planning against
  3. The licence clock decides your timing more than features
  4. What changes between 21, 25 and 29
  5. A planning calendar for the jump
  6. Which path fits your team
  7. For teams in India and the UK
  8. How eCorpIT can help
  9. References

Summary. Yes, Java 29 is the next planned long-term support (LTS) release. Oracle's Java SE Support Roadmap, updated on 20 October 2026, says Oracle intends to ship an LTS every two years and names Java 29, due in September 2027, as the next one, with Premier Support to September 2032 and Extended Support to September 2035. Oracle marks the LTS designation and dates as subject to change. Before it come two non-LTS releases: JDK 27, which reached general availability on 15 September 2026, and JDK 28, scheduled for 9 March 2027. The current LTS is Java 25, released on 16 September 2025, with Oracle Premier Support to September 2030. For teams still on Java 21 the clock is already running: Oracle JDK 21 updates released from 20 October 2026 come under the OTN licence, which is free for personal, development and a few other permitted uses, not general production. Our verdict: if you run Java 21 in production, move to 25 now rather than wait ten months for 29; if you already run 25, plan the 29 upgrade for 2028, after its first update releases, and before free Oracle JDK 25 updates end in September 2028.

About this article. This is for engineering managers, architects and platform teams in India, the UK and the US who run Java services in production. We checked every date on 16 November 2026 against Oracle's support roadmap and price list, the OpenJDK project and JEP pages, and the support pages of Eclipse Adoptium, Amazon and Microsoft. Java 29 does not exist yet, so its dates are Oracle's stated plan, not a commitment. This is not legal or licensing advice, vendor prices change, and no vendor paid for inclusion. Researched with AI assistance and checked against the primary sources listed in the references.

What is confirmed about Java 29, and what is not

Three things are on the record today.

  1. The LTS cadence. Oracle lists Java 8, 11, 17, 21 and 25 as LTS releases and says it intends to make future LTS releases every two years, which puts the next one at Java 29 in September 2027.
  1. The support window Oracle plans. The roadmap table shows Java 29 with general availability in September 2027, Premier Support until September 2032 or later, Extended Support until September 2035 or later, and Sustaining Support indefinitely.
  1. The six-month train. OpenJDK starts a release cycle every June and December by forking the main line, then stabilises it over three months through two rampdown phases and a release-candidate phase. The feature number goes up every six months, so March releases and September releases alternate. That makes 27 in September 2026, 28 in March 2027 and 29 in September 2027.

What is not yet published: OpenJDK has no JDK 29 project page, so there is no schedule or feature list. Following the JEP 3 pattern, we expect the JDK 29 fork in June 2027 and general availability in September 2027, but that is our reading of the process, not an announced date. The LTS label is also a vendor decision. OpenJDK's own pages describe JDK 21 and JDK 25 as LTS releases from most vendors, not from the project itself. Adoptium, Amazon and Microsoft have not yet published Java 29 support dates.

Support dates you are planning against

The table compares the three LTS lines that matter for this decision. Dates come from Oracle's roadmap, the Adoptium Temurin support page, Amazon's Corretto FAQ and Microsoft's OpenJDK support page, all checked on 16 November 2026.

Release GA Oracle Premier Support Oracle Extended Support Eclipse Temurin Amazon Corretto end of life Microsoft Build of OpenJDK
Java 17 September 2021 Ended September 2026 September 2029 At least October 2027 October 2029 September 2027
Java 21 September 2023 September 2028 September 2031 At least December 2029 October 2030 September 2028
Java 25 September 2025 September 2030 September 2033 At least September 2031 October 2032 September 2030
Java 29 September 2027 (planned) September 2032 (planned) September 2035 (planned) Not yet published Not yet published Not yet published

Two caveats. Microsoft lists its dates as the earliest end of support and says it may extend them. Adoptium says it keeps building LTS binaries for as long as the upstream source is maintained.

The non-LTS releases between them have short lives. Oracle supports each one only until the next feature release: JDK 27 until March 2027 and JDK 28 until September 2027. Amazon plans its last Corretto 27 update for January 2027 and end of life in April 2027. Do not put 27 or 28 into production unless you can upgrade every six months.

The licence clock decides your timing more than features

For many organisations the real deadline is set by licensing, not by Java 29.

  • Oracle JDK 21. Updates released from 20 October 2026 are under the Java SE OTN licence, the same terms Oracle uses for 8, 11 and 17 updates. That licence is free for personal, development and some other uses, not for general production use. Oracle tells users who want to stay on permissive terms to move to Oracle JDK 25 or later. Our guide to the Oracle JDK 21 OTN change and 2027 audits covers how to check your exposure.
  • Oracle JDK 25. Free for all users under Oracle's No-Fee Terms and Conditions licence, but Oracle plans to move Oracle JDK 25 updates released after September 2028 to the OTN licence. That is one year after Java 29's planned release, a pattern Oracle also followed for 17 and 21.
  • Oracle JDK 17. Premier Support ended in September 2026. Oracle waives the Extended Support fee from October 2026 to September 2029 for paying customers.

If you need paid Oracle support, the Java SE Universal Subscription is priced per employee, not per server. The price list dated 8 October 2026 gives an annual price of $100 for up to 10 employees, $1,000 for up to 100, $10,000 for up to 500, and $147.20 a year for each employee above 500 up to 2,999. From 3,000 employees the price is monthly per employee, starting at $10.50. Oracle's own worked examples: 800 employees cost $10,000 plus 300 times $147.20, which is $54,160 a year; 3,000 employees cost 3,000 times $10.50 times 12, which is $378,000 a year. The employee count includes contractors and consultants, not only developers.

The free alternative is an OpenJDK build from another vendor. Temurin, Corretto and the Microsoft Build of OpenJDK are all free to use and, as the table shows, support 21 and 25 for years. Switching distributions is usually a change to base images and install scripts, not to code, but test it like any runtime change.

What changes between 21, 25 and 29

From 21 to 25: the features you get now

JDK 25 adds a lot that production teams can use without preview flags.

  • Virtual threads without most pinning. JDK 24 lets virtual threads that block inside synchronized code release their carrier thread, which removes nearly all pinning cases that held back virtual threads on 21. Virtual threads themselves were finalised in 21.
  • Scoped values, module import declarations, compact source files and flexible constructor bodies are final in 25.
  • Faster startup. Ahead-of-time command-line ergonomics and method profiling in 25 make the AOT cache easier to create and more useful.
  • Smaller heaps. Compact object headers became a product option in 25 and are the default from JDK 27, cutting object headers from 96 bits to 64 bits on 64-bit systems.

From 21 to 25: the breaking changes to test for

  • Security Manager. JDK 24 permanently disables it, and it can no longer be enabled.
  • sun.misc.Unsafe memory access. JDK 24 prints a warning the first time any of these methods is called. The calls usually come from older third-party libraries rather than your own code.
  • JNI. JDK 24 warns on JNI use unless native access is enabled for that code, as a step towards restricting it by default.
  • 32-bit x86. JDK 25 removes the 32-bit x86 port.

Run your test suite on 25 with warnings visible. Each warning maps to a library upgrade or a JVM flag, and it is far cheaper to find them now than during the 29 move.

From 25 to 29: what is already in the pipeline

Java 29's contents are not fixed, but it will include everything in 26, 27 and 28. JDK 27 shipped nine JEPs, including G1 as the default collector in all environments and post-quantum hybrid key exchange for TLS 1.3, which applications using the standard javax.net.ssl APIs get by default.

As of 11 November 2026, the JEPs targeted to JDK 28 include value objects as a preview, ahead-of-time code compilation, a final structured concurrency API, a simple JSON API as an incubator, generational mode as the Shenandoah default, and the deprecation of the macOS/x64 port for removal. The list can still change until JDK 28's first rampdown on 3 December 2026.

Two of these matter for planning. Oracle engineers stopped maintaining the macOS/x64 port as of JDK 27, so developers still on Intel Macs should budget for new hardware before the 29 move. And preview features such as value objects need flags and can change, so do not build production code on them until they are final.

A planning calendar for the jump

Dates in the first column are published; the actions are our recommendation.

When What happens What to do
Now to March 2027 Oracle JDK 21 updates are OTN; JDK 25 is the current LTS Move production from 21 to 25, or switch 21 to a free OpenJDK build while you plan
November 2026 Adoptium lists out-of-cycle security updates such as 25.0.5.1 and 21.0.13.1 as next due Apply them like a quarterly update
3 December 2026 JDK 28 rampdown phase one fixes its feature set Review the final JDK 28 JEP list for anything that breaks your stack
19 January 2027 Oracle's next Critical Patch Update Patch every JDK in use, whichever version
9 March 2027 JDK 28 general availability Run your CI on 28 in a non-blocking job
June 2027 (expected) JDK 29 forks from the main line Start testing on JDK 29 early-access builds
September 2027 (planned) Java 29 general availability Upgrade build tools and frameworks; do not rush production
19 October 2027 First Critical Patch Update after Java 29 Begin production moves once your frameworks support 29
September 2028 Oracle JDK 25 updates move to OTN (planned) Be on Oracle JDK 29 or a free OpenJDK 25 build by then

The patch dates come from Oracle, which releases Critical Patch Updates on the third Tuesday of January, April, July and October; the next four are 19 January, 20 April, 20 July and 19 October 2027. The November out-of-cycle builds are listed on Adoptium's release roadmap, and the release dates come from OpenJDK and Oracle.

Frameworks gate the date, not the JDK

Your production date for 29 depends on when your framework supports it. Spring Boot 4.1.2 needs at least Java 17 and is compatible up to Java 27 today, and the 4.2.0 release candidate lists the same range. Support for 28 and 29 has to come in later Spring releases, so plan the Java move alongside your Spring Boot upgrade; our Spring Boot 4.1 support calendar lists those dates. The same applies to build tools, application servers, agents for monitoring and security scanners, and bytecode libraries.

Which path fits your team

You run Java 17 or 21 and use Oracle JDK. Do not wait for 29. Move to 25 in the next two quarters, either on Oracle JDK under the free terms or on a free OpenJDK build. Waiting means ten more months of OTN exposure on 21 and a bigger jump later, with every warning from 22 to 28 arriving at once.

You run Java 21 on Temurin, Corretto or Microsoft's build. You have support until at least September 2028 and in some cases 2030. Skipping 25 and going straight to 29 is possible, but only if you start testing on JDK 28 in March 2027 and accept that the jump covers eight feature releases. Most teams will find two smaller steps cheaper than one large one.

You already run Java 25. Stay. Track JDK 28, test on 29 early-access builds from mid-2027, and move to 29 in 2028 after its first two update releases and once your frameworks list it as supported. If you use Oracle JDK 25 for free, put September 2028 in the plan.

You still run Java 8 or 11. Treat this as a modernisation project, not a version bump. Go to 25 first. Our application modernisation service guide shows how we scope these moves.

For teams in India and the UK

Converted at the ECB reference rates of 13 November 2026, crossed through the euro and rounded to two decimals, a dollar is ₹94.24 or £0.76. On those rates the Oracle example for 800 employees, $54,160 a year, is about ₹51.04 lakh or £41,162; the 3,000-employee example, $378,000, is about ₹3.56 crore or £287,280. Oracle's employee metric includes agents, contractors and consultants, so for an Indian IT services firm a large delivery centre can cost far more than its Java footprint suggests. For many such teams a free OpenJDK build plus internal patching is the cheaper route, provided someone owns the quarterly update cycle. If you are choosing an outside team for the upgrade, our Java development company guide lists the questions to ask.

How eCorpIT can help

eCorpIT is a Gurugram-based technology organisation, founded in 2021, assessed at CMMI Level 5 and MSME certified, with senior-led engineering teams working across AWS, Microsoft and Google platforms. Our application development services team audits your JDK estate and licences, then moves services from Java 8, 11, 17 or 21 to 25 and on to 29 with tests and rollback in place. Talk to us at /contact-us/.

Last updated: 16 November 2026.

References

  1. Oracle Java SE Support Roadmap, updated 20 October 2026 — Oracle
  1. JDK 27 — OpenJDK
  1. JDK 28 — OpenJDK
  1. JDK 25 — OpenJDK
  1. JEP 3: JDK Release Process — OpenJDK
  1. JEP 322: Time-Based Release Versioning — OpenJDK
  1. JDK 21 — OpenJDK
  1. Temurin support — Eclipse Adoptium
  1. Amazon Corretto FAQs — Amazon Web Services
  1. Support roadmap for the Microsoft Build of OpenJDK — Microsoft Learn
  1. Oracle Java SE Universal Subscription Global Price List, 8 October 2026 — Oracle
  1. JEP 491: Synchronize Virtual Threads without Pinning — OpenJDK
  1. JEP 444: Virtual Threads — OpenJDK
  1. JEP 514: Ahead-of-Time Command-Line Ergonomics — OpenJDK
  1. JEP 534: Compact Object Headers by Default — OpenJDK
  1. JEP 486: Permanently Disable the Security Manager — OpenJDK
  1. JEP 498: Warn upon Use of Memory-Access Methods in sun.misc.Unsafe — OpenJDK
  1. JEP 472: Prepare to Restrict the Use of JNI — OpenJDK
  1. JEP 523: Make G1 the Default Garbage Collector in All Environments — OpenJDK
  1. JEP 527: Post-Quantum Hybrid Key Exchange for TLS 1.3 — OpenJDK
  1. JEP 401: Value Objects (Preview) — OpenJDK
  1. JEP 544: Ahead-of-Time Code Compilation — OpenJDK
  1. JEP 543: Structured Concurrency — OpenJDK
  1. JEP 540: Simple JSON API (Incubator) — OpenJDK
  1. JEP 535: Shenandoah GC: Generational Mode by Default — OpenJDK
  1. JEP 541: Deprecate the macOS/x64 Port for Removal — OpenJDK
  1. Critical Patch Updates, Security Alerts and Bulletins — Oracle
  1. System Requirements, Spring Boot 4.1.2 — Spring
  1. System Requirements, Spring Boot 4.2.0-RC2 — Spring
  1. Euro foreign exchange reference rates, 13 November 2026 — European Central Bank

Frequently asked

Quick answers.

01 Is Java 29 an LTS release?
Yes, according to Oracle's plan. Oracle's Java SE Support Roadmap, updated on 20 October 2026, says it intends to ship an LTS release every two years and names Java 29 as the next planned LTS. Oracle notes that the LTS designation and dates are subject to change, so treat it as a firm plan rather than a guarantee.
02 When is Java 29 coming out?
Oracle lists general availability in September 2027. OpenJDK has not yet published a JDK 29 schedule, but the release process forks each version in June or December and ships about three months later, so a mid-September 2027 release is the expected pattern. JDK 28 comes first, on 9 March 2027.
03 How long will Java 29 be supported?
Oracle plans Premier Support until September 2032 or later and Extended Support until September 2035 or later, with Sustaining Support indefinitely. Free OpenJDK distributors such as Eclipse Adoptium, Amazon and Microsoft have not yet published Java 29 dates. They usually announce them near launch, and for Java 25 they range from 2030 to 2032.
04 Should we skip Java 25 and wait for Java 29?
For most teams, no. Java 25 is supported for years, removes nearly all virtual thread pinning and is free under Oracle's current terms. Waiting leaves you on 21, where new Oracle JDK updates are under the OTN licence, and makes the eventual jump cover eight feature releases instead of four.
05 Is Java 27 or Java 28 an LTS release?
No. Both are non-LTS feature releases. Oracle supports each only until the next release ships, so Java 27 until March 2027 and Java 28 until September 2027. Amazon plans Corretto 27 end of life in April 2027. Use them for testing and early access to features, not for long-lived production systems.
06 Will Oracle JDK 29 be free to use in production?
Oracle has not said. Oracle JDK 25 is free for all users under its No-Fee Terms and Conditions licence, with updates after September 2028 moving to the OTN licence. Java 17 and 21 followed the same pattern. Check Oracle's licence terms when 29 ships, or use a free OpenJDK build to avoid the question.
07 What should we test before moving from Java 21 to 25?
Run your full test suite on 25 with warnings visible. Look for code that enables the Security Manager, which JDK 24 permanently disables, warnings from sun.misc.Unsafe memory access, warnings on JNI use, and any 32-bit x86 builds, which 25 removes. Most fixes are library upgrades or explicit JVM flags.
08 When will Spring Boot support Java 29?
No date is published yet. Spring Boot 4.1.2 requires at least Java 17 and lists compatibility up to Java 27, as does the 4.2.0 release candidate. Check the Spring Boot system requirements page for each new release after September 2027 and align your Java upgrade with a version that lists Java 29.

About the author

Manu Shukla

Founder & Director

Founder of eCorpIT. Hands-on engineer leading senior-only delivery for AI apps, custom software, and cloud systems for global clients.

Subscribe

One engineering note a week. No fluff, no spam.

Senior-architect playbooks on AI agents, mobile apps, cloud, security, data, and marketing — delivered every Wednesday.

Past the reading

Read enough. Let's build something.

A senior architect responds in 24 working hours with scope, indicative cost, and a timeline. NDA before any technical conversation.

Loading search…

Browse all guides