Ubuntu Release Cadence: LTS vs. Interim Releases

Ubuntu releases a new version every six months, but only every fourth release is a Long-Term Support (LTS) version. For teams running Ubuntu in production, the choice between LTS and interim releases has real consequences for maintenance overhead, security coverage, and application compatibility.

This article provides a decision framework for 2026. It is written for operations teams, SREs, and infrastructure engineers who need to make a defensible choice about which Ubuntu releases to track. If you are planning a specific upgrade, see the Ubuntu 26.04 LTS upgrade plan.

The Linux hub provides broader system administration resources, and the Linux administration path covers the foundational skills this decision builds on.

LTS vs interim: what the labels mean

LTS releases (every 2 years)

• Support period: 5 years of standard support, extendable to 10 years with Ubuntu Pro
• Security patches: full coverage for main and restricted repositories
• Upgrade path: LTS-to-LTS upgrades are fully supported
• Examples: 22.04, 24.04, 26.04

Interim releases (every 6 months between LTS)

• Support period: 9 months
• Security patches: full coverage during the 9-month window
• Upgrade path: must upgrade to the next release before support ends
• Examples: 24.10, 25.04, 25.10

Decision framework

Choose LTS if:

• You manage servers that need to run for 2+ years without major OS changes
• Your change management process requires long planning cycles
• You need predictable, well-tested package versions
• You run compliance-sensitive workloads where every change must be audited
• Your team does not have bandwidth for twice-yearly OS upgrades

Choose interim if:

• You need the latest kernel for new hardware support
• Your applications depend on newer versions of packages not available in the LTS
• You run development or staging environments that should mirror upcoming production changes
• Your infrastructure is fully automated and OS upgrades are a routine operation
• You are testing compatibility with the next LTS release

Hybrid approach

Many teams use both:

• Production: LTS only
• Development/staging: interim releases to validate compatibility ahead of the next LTS
• Specific workloads: interim releases where newer hardware or software support is required

The 2026 release calendar

| Release | Type | Release date (approx.) | End of support (approx.) | |---|---|---|---| | 24.04 LTS | LTS | April 2024 | April 2029 (standard) | | 24.10 | Interim | October 2024 | July 2025 | | 25.04 | Interim | April 2025 | January 2026 | | 25.10 | Interim | October 2025 | July 2026 | | 26.04 LTS | LTS | April 2026 | April 2031 (standard) |

If you are currently on 24.04 LTS, you can stay there until 2029 with full security support. The upgrade to 26.04 LTS is recommended but not urgent.

If you are on any interim release, you must upgrade before its support ends or you will stop receiving security patches.

Upgrade paths and constraints

LTS to LTS

You can upgrade directly from one LTS to the next (e.g., 24.04 → 26.04). Canonical recommends waiting for the .1 point release (e.g., 26.04.1) before upgrading production systems.

Interim to interim

Each interim release can only upgrade to the immediately following release. You cannot skip: 25.04 → 25.10 → 26.04, but not 25.04 → 26.04 directly.

Interim to LTS

The last interim release before an LTS (e.g., 25.10) can upgrade directly to the LTS (26.04).

Security considerations

Patch timeliness

Both LTS and interim releases receive security patches promptly for packages in main and restricted. The difference is the support window: 5+ years for LTS vs 9 months for interim.

Kernel security

LTS releases receive kernel security patches for the entire support period. The kernel version itself does not change (e.g., 6.8 for 24.04), but backported fixes are applied. Interim releases ship newer kernels with a shorter patch window.

End-of-life risk

The biggest security risk with interim releases is running past end-of-life. If your team misses an upgrade deadline, the system stops receiving security patches with no grace period.

Operational trade-offs

• LTS reduces upgrade frequency but means running older package versions. You may need PPAs or Snap packages for newer software.
• Interim releases provide fresher packages but require upgrades every 6–9 months, which is operationally expensive for large fleets.
• Ubuntu Pro extends LTS support to 10 years but comes with licensing costs.
• Container-based workloads can decouple the host OS from application packages, reducing the pressure to upgrade for newer software versions.

Recommendations for 2026

1. If you are on 22.04 LTS: plan your upgrade to 26.04 LTS for Q3/Q4 2026 (after the .1 release).
2. If you are on 24.04 LTS: no urgency. Stay on 24.04 and evaluate 26.04 in 2027.
3. If you are on any interim release: upgrade to 26.04 LTS as soon as the .1 release is available to get back on a stable support track.
4. For new deployments: use 26.04 LTS (after the .1 release) for production and interim releases only for testing.

Further reading on EBooks-Space

• Linux topic hub — curated system administration reading lists
• Linux Administration learning path — structured progression through Linux skills
• Ubuntu 26.04 LTS upgrade plan — the tactical upgrade guide