Long-Term Support (LTS) Fundamentals
What you'll learn: How organizations maintain multiple supported software versions simultaneously through Long-Term Support policies.
What is LTS?
Long-Term Support (LTS) releases are special software versions that receive extended maintenance, security patches, and bug fixes for a predefined period—often years longer than regular releases. While normal versions might be supported for months, LTS versions can be maintained for 3-5 years or more.
Think of LTS like a car model manufacturers continue servicing with parts and recalls long after newer models arrive. Organizations running critical systems can't upgrade every few months, so they rely on these stable, well-maintained versions.
LTS Lifecycle Policies
A typical LTS lifecycle includes:
- Active support phase: Full feature backports, bug fixes, and security patches
- Maintenance phase: Security patches and critical bug fixes only
- End-of-life (EOL): No further updates; users must upgrade
For example, an LTS version released in January 2023 might have active support through January 2025, maintenance through January 2027, then reach EOL. Meanwhile, new LTS versions release on a predictable schedule (e.g., every two years).
Why Multiple Supported Versions?
Organizations maintain multiple LTS versions because:
- Risk mitigation: Upgrades introduce breaking changes; LTS gives breathing room
- Regulatory compliance: Industries like healthcare and finance need stable, auditable versions
- Resource constraints: Large codebases can't upgrade constantly
- Customer diversity: Different clients have different upgrade timelines
This means release engineering teams backport security fixes across multiple branches simultaneously, testing each version independently.
Key Takeaway: LTS releases provide extended support for stable software versions, allowing organizations to balance security and stability while managing upgrade schedules according to their risk tolerance and resource capacity.