Fact-checked by Grok 2 weeks ago

Long-term support

Long-term support (LTS) is a software release and lifecycle management policy in which a stable version of computer software or an operating system is maintained with extended updates, including security patches, bug fixes, and sometimes feature enhancements, for a significantly longer duration than interim or standard releases. This approach prioritizes stability and reliability, particularly for environments where frequent upgrades may disrupt operations. The rationale behind LTS stems from the need to balance innovation with dependability in . Developers release LTS versions periodically—often every two years for major projects—to allow users ample time to deploy and integrate the software without the pressure of short support cycles. For instance, in open-source distributions like , LTS editions receive free security maintenance for an initial five years, extendable to ten years with Ubuntu Pro (Expanded Security Maintenance) and up to fifteen years with the add-on, ensuring long-term viability for servers and . Similarly, Microsoft's .NET framework designates LTS releases with three years of support, focusing on critical fixes while encouraging eventual migration to newer versions. LTS policies vary by vendor but commonly contrast with short-term support (STS) or interim releases, which receive updates for shorter periods, typically 9 months to 2 years, to deliver cutting-edge features more rapidly. Prominent examples include , which offers up to ten years of support through phased updates and extended life cycle add-ons, and IBM's software products, typically backed for two to five years under customer agreements. This model has become standard in the industry, enabling organizations to plan upgrades methodically while minimizing security risks from unsupported software.

Overview

Definition

Long-term support (LTS) is a software release in which a designated version of a software product receives extended beyond the typical lifecycle of standard releases, often spanning 3 to 10 years, to ensure ongoing stability and for users who prioritize reliability over frequent updates. This typically encompasses patches, critical bug fixes, and occasionally minor feature updates, all delivered without introducing major changes that could disrupt existing deployments. The contrasts with short-term (STS) releases, which receive updates for a shorter duration, usually 6 to 18 months, encouraging quicker adoption of newer versions. A key aspect of LTS involves the distinction between major version releases explicitly labeled as LTS and non-LTS variants, with developers announcing binding support timelines at the time of release to allow users to plan accordingly. This commitment ensures that LTS versions maintain binary compatibility, meaning fixes are backported from newer branches to avoid breaking existing codebases or requiring recompilation. For instance, in open-source projects, LTS focuses on preserving the version's functionality while addressing vulnerabilities, thereby supporting environments where upgrades may be infrequent. The formal designation and policy of LTS originated in open-source communities in 2006, with early implementations in distributions like Ubuntu's first LTS release that year, building on prior enterprise practices of extended support; it has since become applicable to both open-source and proprietary software, including kernels and enterprise tools. By providing a stable foundation, LTS enables long-term deployment in critical systems without the risks associated with rapid iteration.

Historical Development

The concept of long-term support (LTS) in software built on extended maintenance practices that originated in the enterprise sector during the , drawing from mainframe and Unix environments where was paramount for mission-critical operations. Commercial Unix vendors such as and offered prolonged support for their systems, including security patches and compatibility guarantees, to sustain enterprise deployments in high-availability settings. A pivotal advancement came in the open-source domain with the formalization of LTS for the . In 2006, kernel maintainer designated version 2.6.16 as the first official LTS release, committing to ongoing bug fixes and security updates to address the growing needs of and users who required predictable . That same year, Canonical introduced the LTS branding for 6.06 (Dapper Drake), promising five years of free security maintenance for desktops and servers, which helped popularize the model among Linux distributions and enterprises transitioning from systems. LTS practices expanded beyond Unix-like systems in the late 2000s and 2010s. adopted an extended support phase for , announced in October 2009 alongside its release, guaranteeing security updates until January 2020 to meet corporate demands for prolonged usability in business environments. In the mobile space, in 2017 extended LTS branches to six years of maintenance, enabling Android device manufacturers to backport security fixes more reliably without frequent kernel upgrades. This extension was reaffirmed in 2024 with 's commitment to provide four additional years of support for stable LTS kernels used in Android, totaling six years as of 2025. The growth of LTS was driven by enterprise priorities for reliability amid economic uncertainty in the early 2000s. Concurrently, the maturation of open-source ecosystems in the mid-2000s, bolstered by initiatives like the founded in 2007, empowered community-led maintenance efforts that scaled LTS without . By 2025, LTS has permeated and frameworks amid rising demands for production-grade reliability. Enterprise, for instance, offers up to three years of security patches and bug fixes for designated versions, supporting enterprise ML workflows. In cloud-native environments, trends have shifted toward "evergreen" models, where continuous incremental updates via automated patching replace fixed LTS periods to ensure perpetual compatibility and security in dynamic infrastructures.

Characteristics

Support Duration and Phases

Long-term support (LTS) durations vary by software type and provider, typically ranging from 3 to 5 years for consumer-oriented releases to 5 to 10 years for enterprise-grade systems. For instance, LTS releases receive 5 years of standard , extendable to 10 years through Expanded Security (ESM). In contrast, (RHEL) versions 8, 9, and 10 offer a 10-year lifecycle, comprising full and phases followed by an extended life . RHEL 7, released in , exemplifies this with concluding in 2024 after 10 years, including an optional extended until 2028. stable releases follow a 5-year total duration, with 3 years of full and 2 years of LTS. LTS lifecycles are structured into distinct phases to balance stability, resource allocation, and user needs. The initial phase, often called full or mainstream support, provides comprehensive updates including security patches, bug fixes, and sometimes minor enhancements, typically lasting 5 years for many enterprise products or 3 years for some open-source distributions like Debian, depending on the product. This transitions to a maintenance phase focused on security and critical fixes only, excluding new features, which extends support for another 2 to 5 years. An extended phase may follow, offering security updates exclusively—typically on a paid basis—for 1 to 5 additional years, as seen in RHEL's Extended Life Cycle Support (ELS) add-on or Ubuntu's ESM. End-of-life (EOL) marks the final phase, where support ceases entirely, accompanied by announcements providing migration guidance to newer versions. For example, as of November 2025, Ubuntu 20.04 LTS standard support ended in April 2025, with ESM extending to 2030. Several factors influence LTS duration and phase lengths, including the codebase's complexity, community involvement, and underlying business models. Larger codebases in , such as RHEL, necessitate longer support to manage extensive dependencies and testing. Community-driven projects like rely on volunteer efforts, resulting in shorter but targeted LTS extensions funded partly by sponsors. Commercial models play a key role: free core support with optional paid extensions, as in ESM, contrasts with subscription-based full coverage in RHEL, enabling sustained revenue for prolonged phases. Phase structures can vary; for instance, LTS includes an initial Active sub-phase with limited new features before transitioning to maintenance. Phase transitions are tracked via version numbering and , such as "LTS until YYYY" designations. For example, 20.04 LTS notes specify until April 2025 for standard phases, with ESM extending to 2030. employs terms like "oldstable" for the previous release during part of full , shifting to LTS for the final 2 years, with explicit announcements for phase changes. These metrics ensure predictability, allowing users to plan upgrades aligned with timelines.

Types of Updates Provided

In long-term support (LTS) releases, security updates form the cornerstone of maintenance, with a primary emphasis on patching vulnerabilities through backported fixes to minimize disruptions to existing codebases. These updates are typically prioritized based on severity, adhering to standardized frameworks such as the system for identification and scoring, ensuring that critical threats are addressed promptly without introducing new dependencies or API alterations. For instance, backporting involves adapting patches from newer versions to the LTS branch, maintaining the original architecture's integrity while resolving exploits like buffer overflows or privilege escalations. Bug fixes in LTS are restricted to critical and high-severity issues that impact stability or functionality, explicitly excluding enhancements or low-priority corrections to preserve . Issues are triaged through dedicated processes, often using LTS-specific branches where maintainers evaluate reports against criteria like and user impact, resulting in selective merges that avoid broader refactoring. This approach ensures that only defects posing risks to environments—such as crashes or —are resolved, fostering reliability without the overhead of comprehensive testing for non-essential changes. Compatibility guarantees are a defining feature of LTS, with policies enforcing no breaking changes to APIs, configurations, or behaviors, thereby supporting legacy integrations and extending hardware compatibility for older devices. This stability enables seamless operation in environments reliant on deprecated components, such as enterprise systems interfacing with legacy peripherals, by prioritizing backward compatibility in all updates. Feature inclusion varies by project and phase but remains highly limited overall, confined to rare minor adjustments necessitated by regulatory requirements, like adaptations for data privacy standards, while major innovations are withheld to prevent scope creep and maintain a lean, predictable release. Updates are delivered via incremental point releases, such as progressing from version 1.0 to 1.0.5, which bundle cumulative fixes into stable packages distributed through software repositories or dedicated enterprise portals for controlled access and verification. This mechanism allows users to apply updates selectively, often via automated tools that verify integrity before deployment, ensuring minimal in sustained environments.

Rationale and Benefits

Advantages for End Users

Long-term support (LTS) releases provide end users with predictable timelines for , allowing individuals to plan upgrades without the pressure of forced obsolescence or sudden disruptions in personal computing setups. For instance, LTS versions offer five years of standard free security updates and support for desktop users, extendable to 10 years via Ubuntu Pro (free for personal use on up to five machines). This stability is achieved by focusing on hardening existing features rather than introducing new ones, minimizing compatibility issues and reducing the need for constant reconfiguration in home environments. Security remains a key assurance for users holding onto systems longer, as LTS ensures ongoing patches for vulnerabilities even after standard support ends for non-LTS releases. In Ubuntu, security fixes are backported to LTS versions without forcing upgrades, benefiting non-technical users who prefer to avoid the risks associated with frequent updates. Similarly, (RHEL) provides a 10-year support lifecycle, addressing critical security issues throughout, which extends to individual users leveraging compatible distributions for personal stability. This approach mitigates risks in long-held systems, particularly for those in offline or low-connectivity scenarios where timely updates might otherwise be challenging. LTS contributes to cost savings by extending and eliminating the need for retraining or repeated installations, lowering the total ownership cost for end users. Point releases in LTS maintain for new desktop across the five-year cycle, allowing older devices to run supported software without immediate replacement. RHEL's binary across minor releases further reduces expenses, as applications and configurations persist without rework, a benefit applicable to home users via free clones like . In resource-constrained environments, such as older devices or setups with limited , LTS enhances by prioritizing reliability over cutting-edge features. This model supports applications in and home use, preventing from unsupported software transitions; for example, LTS has enabled sustained use in personal learning tools without compatibility breaks. Microsoft's Long-Term Servicing Channel (LTSC) offers extended stability for specialized enterprise devices such as medical equipment or industrial controllers, ensuring continued functionality without the overhead of semi-annual feature updates.

Advantages for Organizations and Developers

Long-term support (LTS) releases facilitate for organizations by enabling compliance with stringent industry regulations, such as the Payment Card Industry Data Security Standard (PCI-DSS), through certified stable versions that receive extended security patches and vulnerability remediation. These releases ensure timely updates to address (CVEs), reducing average exposure time from 98 days to as low as 1 day in supported environments. In production settings, this stability minimizes unplanned downtime by avoiding the disruptions associated with frequent major upgrades, allowing mission-critical systems to operate reliably without compromising security. LTS also optimizes within development teams, permitting engineers to concentrate on innovative projects rather than routine of systems, as vendors provide dedicated support for stable branches. This approach proves particularly cost-effective for large-scale organizations, where support contracts from providers like cover patching and compliance without requiring in-house expertise for every update. By segregating responsibilities, teams can scale efficiently, directing human and financial resources toward high-value development initiatives while ensuring operational continuity. Furthermore, LTS enhances ecosystem stability by fostering seamless third-party integrations and reliability, especially in systems and deployments where predictability is essential. For instance, LTS versions integrate with major platforms, providing consistent APIs and security profiles that support vendor ecosystems without breaking during extended lifecycles. This reliability bolsters organizational s by reducing integration risks across hardware, software, and services. Organizations benefit from a balanced approach to through LTS, which allows bleeding-edge on interim releases for experimentation while maintaining robust, unchanging backends for production workloads. This duality enables teams to advanced features without destabilizing core , promoting sustained progress alongside reliability. Economically, LTS models generate for providers via extended support subscriptions, such as Canonical's Pro, which offers a total of 12 years of (expanded to 15 years as of November 2025 with the Legacy add-on) for enterprise clients.

Implementation

Release Strategies

Long-term support (LTS) releases are designated based on criteria emphasizing stability and maturity, typically after extensive testing to ensure the branch meets enterprise-grade reliability standards. For instance, projects select versions that have undergone rigorous validation, including audits and benchmarks, before labeling them as LTS. Frequency of designation varies, but a common practice is to release LTS versions every two years, as seen in Ubuntu's cycle where LTS editions occur every fourth semi-annual release in of even-numbered years. Branching models for LTS often leverage version control systems like to create forks from main development lines, allowing isolated without disrupting ongoing . In release branching strategies, a dedicated long-lived branch is forked from the mainline once a is deemed , enabling backports of critical fixes while synchronizing select upstream changes to avoid divergence. This approach supports multiple active s, with tools facilitating merges from feature branches into the LTS fork only after thorough review. Announcement practices for LTS releases involve publishing detailed public roadmaps that outline commitments, timelines, and validation milestones to build user trust and facilitate planning. These typically include phases for community testing and feedback, culminating in a formal release declaration with on expected duration. For example, organizations designate LTS at least annually, announcing backport policies for security and critical updates. Hybrid approaches combine LTS with short-term releases to balance and , such as maintaining a stable branch for alongside testing branches for upcoming features. In Debian's model, the receives full support for three years followed by two years of LTS, while testing and unstable branches allow of new packages, with promotions to stable only after meeting release criteria like bug resolution and package migration. This enables organizations to use LTS for core infrastructure while experimenting with interim updates. As of 2025, LTS strategies have adapted to trends by emphasizing containerized images, providing immutable, lightweight distributions that align with orchestration tools like for scalable deployments. These images inherit the LTS support lifecycle, ensuring patches and compatibility in cloud-native environments without requiring full OS upgrades.

Maintenance Processes

Maintenance processes for long-term support (LTS) versions involve structured workflows to identify, validate, and apply updates while preserving . Bug and typically occur through dedicated issue trackers such as or , where LTS-specific queues separate critical issues from general ones. In projects like , assesses vulnerabilities via CVE announcements, assigning severity levels to guide backporting decisions for and fixes. Severity-based policies ensure high-impact bugs, such as flaws, receive immediate attention, while lower-priority issues may be deferred or rejected if they risk introducing regressions. Team structures for LTS sustainment often include dedicated maintainers or vendor-specific groups responsible for oversight. For instance, employs a specialized team to handle LTS branches, coordinating upstream integrations and backports. In open-source ecosystems like the , LTS maintainers—often volunteers or company-sponsored—review and merge patches, supported by community contributions submitted as merge proposals or pull requests. These teams enforce guidelines to maintain compatibility, relying on collaborative platforms like or for proposal reviews. Testing protocols emphasize on isolated LTS branches to prevent disruptions. Automated / (CI/CD) pipelines run comprehensive suites, including , , and security tests, before patches are merged. For , CI/CD workflows incorporate automated checks to verify fix efficacy across environments, ensuring no unintended side effects. focuses on core functionalities, with tools like Jenkins or CI automating builds and deployments specific to LTS codebases. As LTS periods conclude, end-of-support handling includes issuing notices well in advance to inform users. Projects like move repositories to archives such as old-releases.ubuntu.com after the support window, preserving to final updates. provides migration tools, such as the Upgrade Tool or Leapp framework, to automate transitions to newer versions, alongside extended life phase options for critical systems. These measures facilitate smooth upgrades, with vendors like offering phased announcements detailing timelines and alternatives. Automation tools streamline fix application through scripts for cherry-picking commits from main branches to LTS ones, using Git's native cherry-pick command to selectively apply changes without full merges. Specialized scripts, such as Python's cherry-picker, automate backporting in maintenance branches by identifying compatible commits. Integration with package managers like APT for Debian-based systems or YUM/DNF for ensures patches are distributed via secure repositories, enabling automated updates with dependency resolution. For example, Ubuntu's security team pushes backported packages to LTS repositories, allowing users to apply fixes seamlessly via apt update and apt upgrade.

Examples

In Operating Systems

Long-term support (LTS) in operating systems emphasizes extended maintenance periods to ensure , , and for , particularly in server and enterprise environments. Linux distributions have pioneered robust LTS models, with offering five years of standard support followed by five years of Expanded Security Maintenance (ESM) for its LTS releases. For instance, 22.04 LTS (Jammy ), released in April 2022, receives maintenance updates until April 2027, with ESM extending patches to April 2032 for subscribers. Similarly, (RHEL) provides a 10-year lifecycle, balancing full support, maintenance, and extended phases; RHEL 9, launched in May 2022, remains in full support until May 2027 and maintenance support until May 2032. These models allow organizations to deploy stable systems without frequent major upgrades, reducing operational disruptions. Microsoft's Windows implements LTS through differentiated support tiers, contrasting consumer editions with specialized long-term branches. Windows 10's mainstream and extended concluded on October 14, 2025, after which only paid Extended Security Updates (ESU) are available for up to three additional years. In contrast, the Long-Term Servicing Channel (LTSC) targets and scenarios with minimal feature changes; Windows 10 Enterprise LTSC 2019, released in November 2018, receives security and stability updates until January 9, 2029. This approach suits environments like medical devices or industrial controls where predictability outweighs new features. Other operating systems adopt tailored LTS strategies to address diverse ecosystems. 's Long Term Support extends the lifecycle of stable releases beyond the initial three years of full updates, focusing on security for key architectures; 10 (Buster), released in July 2019, concluded its LTS phase on June 30, 2024, after nearly five years. Apple's macOS provides security updates for the current version and the three immediately preceding major releases, ensuring compatibility for supported hardware without a formal LTS designation; as of late 2025, this covers macOS 16 (current release), (15), Sonoma (14), and Ventura (13), though Ventura's support ends on November 30, 2025, and full patch guarantees apply primarily to the latest release. LTS implementations in operating systems drive market stability, particularly in servers, where Linux distributions hold approximately 55% share in enterprise environments as of 2024, with LTS variants like RHEL and Ubuntu dominating due to their reliability. However, challenges arise in kernel maintenance, as LTS versions must incorporate hardware support for evolving technologies—such as newer CPUs and GPUs—while avoiding performance regressions on legacy systems, often requiring backporting fixes rather than upstream merges. In 2025, Red Hat announced RHEL 10 as its latest LTS release, emphasizing AI-optimized features like integrated generative AI for command-line troubleshooting and quantum-resistant cryptography to future-proof enterprise deployments. These advancements underscore LTS's role in adapting to emerging demands without compromising core stability.

In Applications and Frameworks

In programming languages and runtimes, long-term support is commonly provided to ensure stability for production environments. For instance, designates even-numbered major versions as LTS releases, with version 20 (codenamed Iron), released on April 18, 2023, entering Active LTS on October 18, 2023, and receiving active support until October 18, 2024, followed by maintenance support until April 30, 2026. This 30-month total support period includes critical bug fixes and security updates during both phases. , while lacking an official LTS designation from the , benefits from community-driven efforts to extend support for versions like 3.8 and later, with official security fixes provided for five years per release (e.g., Python 3.8 supported until October 14, 2024), and additional backports through third-party distributions for enterprise use. Web servers and databases also adopt LTS models to maintain reliability in infrastructure. The 2.4 branch, released in March 2012, continues to receive ongoing security patches and bug fixes as the primary stable version, with no announced end-of-life date, making it a LTS for web hosting. 8.0, introduced as an LTS release in April 2018, provides bug fixes and security updates until April 2026 under Oracle's commercial support policy, catering to enterprise database deployments. Frameworks for application development frequently incorporate LTS to align with enterprise needs. Microsoft's .NET 8, released on November 14, 2023, offers three years of LTS support until November 10, 2026, including monthly security and reliability updates for cross-platform applications. , through provider-specific long-term channels, supports versions like 1.28 (released August 2023) with extended maintenance in environments such as Kubernetes Service (AKS), where LTS extends patch support to 24 months for stability in container orchestration. Niche applications in creative and desktop domains leverage LTS for specialized workflows. designates select releases as LTS, such as version 4.2 (July 2024) supported until July 2026 with two years of bug fixes and security updates, enabling consistent tooling for in the . , used for building cross-platform desktop apps, aligns its stable branches with LTS versions to provide reliable runtime support, ensuring apps like remain secure without frequent rebuilds. A notable trend is the increasing adoption of LTS in tools to support production pipelines. PyTorch version 1.13, released in October 2022, has seen extended community and vendor support in certain ecosystems until mid-2025, reflecting the demand for stable tensors and model training in ML frameworks. This shift underscores how LTS facilitates long-running deployments amid rapid innovation.

Comparisons and Alternatives

Versus Standard Release Cycles

Standard release cycles in typically involve fixed-interval updates every 6 to 12 months, delivering comprehensive feature enhancements, security patches, and improvements while providing short-term support, often lasting 9 to 13 months per version. For instance, Ubuntu's interim releases occur biannually in and , introducing new capabilities but with only 9 months of maintenance, while follows a similar semiannual schedule with approximately 13 months of support per release. These cycles emphasize rapid iteration to keep pace with evolving technologies and user needs. In contrast, long-term support (LTS) versions prioritize stability and extended maintenance over frequent innovation, often spanning 3 to 5 years or more, focusing on bug fixes and security updates without introducing major new features. Standard cycles enable quicker access to cutting-edge and tools but come with shorter support windows of 1 to 2 years, requiring more frequent upgrades. This difference means LTS reduces the operational burden of constant updates, though it may leave users with older features until the next LTS cycle. The trade-offs between the two approaches are significant: LTS minimizes upgrade frequency and migration efforts, fostering consistency in production environments, but risks incorporating outdated functionalities that could hinder competitiveness. Conversely, standard cycles facilitate swift incorporation of fixes and innovations, benefiting , yet they increase the administrative overhead of regular transitions and potential issues. Standard releases suit developers and teams requiring the latest for experimentation and , whereas LTS is ideal for systems where reliability and minimal disruption outweigh the need for novelty. Some projects adopt hybrid models, offering both standard and LTS options to balance these priorities. For example, the Eclipse Foundation provides quarterly simultaneous releases for ongoing innovation alongside an optional LTS program that extends maintenance for selected versions, allowing users to choose based on their stability needs.

Versus Rolling Releases

Rolling releases represent a distribution model characterized by perpetual, incremental updates that integrate the latest fixes, features, and software versions without discrete version numbering or fixed release cycles. Examples include Arch Linux, which employs a rolling-release system enabling one-time installation followed by continuous upgrades to maintain the most current packages, and openSUSE Tumbleweed, a tested rolling release providing the latest stable software versions through frequent, snapshot-based updates. In contrast to long-term support (LTS) models, which provide versioned snapshots with extended, bounded maintenance periods for stability and predictability, rolling releases maintain an always-evolving, unversioned system state that prioritizes currency over fixed milestones. This fundamental difference means LTS distributions, such as , freeze features at specific points to ensure rigorous testing and long-term compatibility, while rolling models like push updates as they stabilize, potentially introducing instability from untested interactions. The trade-offs between the two models highlight a between agility and reliability: rolling releases appeal to users seeking immediate access to cutting-edge hardware support and software innovations, but they expose systems to occasional regressions or breakage from rapid changes, as seen in rare but disruptive issues in updates. Conversely, LTS ensures auditability and reproducibility essential for compliance-driven environments, such as enterprise servers, by guaranteeing consistent behavior over years without the risk of mid-support disruptions. Adoption contexts further delineate their suitability: rolling releases thrive in personal tinkering and enthusiast scenarios where users value the latest tools and are equipped to troubleshoot, as with desktop setups running openSUSE Tumbleweed for its snapshot rollback capabilities. LTS, however, dominates deployments and production environments where and minimal downtime are paramount, exemplified by LTS in data centers for its five-year support window. Emerging overlaps in some projects blend rolling dynamism with LTS-like stability through mechanisms like package pinning; for instance, NixOS's unstable channel functions as a for the latest packages, but users can pin specific versions or dependencies to achieve reproducible, stable configurations akin to LTS without full system freezes.

References

  1. [1]
    Ubuntu release cycle
    LTS or 'Long Term Support' releases are published every two years in April. LTS releases are the 'enterprise grade' releases of Ubuntu and are used the most.
  2. [2]
    The official .NET support policy
    Each .NET release is defined as either Standard Term Support (STS) or Long Term Support (LTS), at the beginning of the release. STS releases ...
  3. [3]
    What is an Ubuntu LTS release?
    Apr 17, 2020 · An Ubuntu LTS is a commitment from Canonical to support and maintain a version of Ubuntu for ten years, with the initial five years available for free.
  4. [4]
    Ubuntu Releases
    There are 2 types of Ubuntu releases: Interim and LTS. Each Ubuntu LTS is maintained for 10 years total: 5 years of standard support + 5 years of ESM.
  5. [5]
    NET and .NET Core official support policy
    Long Term Support (LTS). LTS releases are supported for three years after the initial release. · Standard Term Support (STS). STS releases are supported for one ...
  6. [6]
    Red Hat Enterprise Linux Life Cycle
    Extended Life Cycle Support Long-Life Add-On - Term 5 (begins January 1, 2027 - ends December 31, 2027). Red Hat Enterprise Linux 6 ELS delivers certain Red Hat ...
  7. [7]
    IBM software support lifecycle policies
    Most IBM Customer Agreement (ICA) license type software products have a two-to-five-year support period and already provide advance notice of withdrawal from ...Missing: long- | Show results with:long-
  8. [8]
    https://www.ibm.com/support/pages/ibm-software-support-lifecycle-policies
  9. [9]
    Windows Server Servicing Channels - Microsoft Learn
    Jun 25, 2025 · The Long-Term Servicing Channel (LTSC) provides a longer term option focuses on providing a traditional lifecycle of quality and security ...
  10. [10]
    Releases - The Linux Kernel Archives
    May 26, 2025 · Each new longterm kernel usually starts with only a 2-year projected EOL that can be extended further if there is enough interest from the ...
  11. [11]
    10. DPDK Stable Releases and Long Term Support
    Backporting should be limited to bug fixes. All patches accepted on the main branch with a Fixes: tag should be backported to the relevant stable/LTS branches, ...Missing: binary | Show results with:binary
  12. [12]
    Timeline : Ubuntu - Launchpad
    In the wake of the release of Ubuntu 6.06 LTS, Edgy ... Ubuntu 6.06 LTS (The Dapper Drake Release) is the first long-term-supported release of Ubuntu.
  13. [13]
    Linux Kernel Milestones in 2011
    Dec 20, 2011 · Another important milestone in 2011 is the announcement of long term kernel support for consumer devices. The Long Term Support Initiative ...
  14. [14]
    LTSC: What is it, and when should it be used?
    Nov 29, 2018 · The Long-Term Servicing Channel (LTSC) is designed for Windows 10 devices and use cases where the key requirement is that functionality and features don't ...
  15. [15]
    The IBM System/390
    The operating system, OS/390, was introduced in late 1995 to provide a fully functional multiple virtual storage package. OS/390 improved the realizability ...Missing: contracts | Show results with:contracts
  16. [16]
    The long, slow death of commercial Unix | Network World
    Feb 13, 2019 · Bowers expects a long-tail decline in Unix that might last 20 years. “As a viable operating system, it's got at least 10 years because there's this long tail.
  17. [17]
    Linux Kernel Release Model - - Kroah
    Feb 5, 2018 · The first LTS kernel was 2.6.16, released in 2006. Since then, a new LTS kernel has been picked once a year. That kernel will be maintained by ...
  18. [18]
    Announcing Ubuntu 6.06 LTS - Ubuntu Fridge
    Ubuntu 6.06 LTS will be the first Ubuntu release with a long-term support cycle: free security updates and commercial technical support will ...
  19. [19]
    Windows 7 - Microsoft Lifecycle
    Windows 7 follows the Fixed Lifecycle Policy. ... Support for this product has ended. See migration guidance below. Support dates are shown in the Pacific Time ...
  20. [20]
    Android users rejoice! Linux kernel LTS releases are now good for 6 ...
    Sep 29, 2017 · Googler Iliyan Malchev announced that Linux LTS (Long Term Support) kernels were switching from a two-year lifecycle to a whopping six years of support.
  21. [21]
    Opinion | The Next Economic Bubble Is Here - The New York Times
    Oct 23, 2025 · So, even after the bubble burst, even after this investment was collapsing, productivity growth was actually very, very strong. ... dot-com boom.
  22. [22]
    TensorFlow Enterprise: Supported, scalable, and seamless ...
    Oct 31, 2019 · For certain versions of TensorFlow, we will provide security patches and select bug fixes for up to 3 years. These versions will be supported on ...
  23. [23]
    How to harness the power of incremental updates - Red Hat
    Jan 18, 2022 · Achieving a state of evergreen IT is an activity in transforming IT delivery. It takes a concerted effort and a dedicated focus on making it happen.
  24. [24]
    Ubuntu - endoflife.date
    Oct 11, 2025 · LTS or “Long-Term Support” releases are published every two years in April. Every six months between LTS versions, Canonical publishes an ...
  25. [25]
    Red Hat Enterprise Linux | endoflife.date
    Aug 10, 2025 · Red Hat Enterprise Linux versions 5, 6, and 7 each deliver ten years of support in Full Support, Maintenance Support 1 and Maintenance Support 2 Phases ...Missing: durations | Show results with:durations
  26. [26]
    LTS - Debian Wiki
    Debian Long Term Support (LTS) is a project to extend the lifetime of all Debian stable releases to (at least) 5 years.LTS/Using · Extended Long Term Support · Funding the Debian LTS project · Stretch
  27. [27]
    Fixed Lifecycle Policy - Microsoft Learn
    Feb 21, 2023 · Both the Mainstream Support and Extended Support phases for software require a product's supported service pack to be installed to continue ...Missing: standard | Show results with:standard
  28. [28]
    Ubuntu 20.04 LTS Standard Support has ended. Here's how to ...
    Nov 21, 2024 · Ubuntu 20.04 LTS (Focal Fossa) has reached the end of its standard five-year support window on 31 May 2025. It's time to start thinking about your options for ...
  29. [29]
    DebianReleases - Debian Wiki
    Aug 14, 2025 · Version. Code name. Freeze length. Time from previous release. Time from next release up to EOL ; 1.2. Rex. 178 days ; 1.3. Bo. 175 days.DebianTrixie · DebianTesting · DebianBullseye
  30. [30]
    Debian | endoflife.date
    Sep 10, 2025 · Debian Long-Term Support (LTS) is a project to extend the lifetime of all Debian stable releases to (at least) 5 years on a limited set of ...
  31. [31]
    Security updates - Ubuntu documentation
    This means that security updates will not generally introduce new functionality and stability is achieved by maintaining backward compatibility.
  32. [32]
    'Backporting' Challenges in Cyber Security | Edgescan
    Mar 3, 2025 · Backporting is the process of taking security patches, bug fixes, or feature updates from a newer version of software and applying them to an older version ...
  33. [33]
    Node.js Release Working Group - GitHub
    Maintenance - Critical bug fixes and security updates. New features may be added at the discretion of the Release team - typically only in cases where the new ...
  34. [34]
    Development — Debian LTS Team documentation
    Backport the fixes to the version in LTS. Make sure that each fix was approved by the upstream project (e.g. committed to their development repository), ...<|control11|><|separator|>
  35. [35]
    CKEditor 5 LTS Edition
    Released once every two years, each LTS version provides up to 3 years of guaranteed security and compatibility fixes with zero breaking changes.
  36. [36]
    Chapter 1. Software Releases and Long-Term Support (LTS) - VoltDB
    The goal of the LTS release is to clearly identify the most stable version available for each major release. Installing the subsequent point releases ensures ...Missing: delivery mechanisms repositories
  37. [37]
    LTS - Ubuntu Wiki
    ### Summary of Benefits for Individual Users of Ubuntu LTS Releases
  38. [38]
    Ubuntu Expanded Security Maintenance
    Expanded Security Maintenance provides ongoing security fixes for Ubuntu, the Linux kernel and packages in Ubuntu repositories packages beyond the five-year ...Platform Security · Kernel Livepatch · Securing open source through...
  39. [39]
    Enable PCI-DSS compliance with Ubuntu Pro
    Ubuntu Pro supports the PCI-DSS requirement to remediate software vulnerabilities for the OS and applications in a timely manner. It also allows rebootless ...Your Pathway To Pci-Dss... · Choose Trusted Open Source · Resources
  40. [40]
    The world's favourite enterprise OS | Canonical
    Ubuntu gives you secure access to the widest open source software library. Reduce your average CVE exposure from 98 days to 1 on average and comply with the ...
  41. [41]
    Canonical gives businesses the Ubuntu Advantage
    Jun 8, 2010 · Ubuntu Advantage provides simplicity and an easier way for businesses to purchase the necessary tools and services to manage, support and use their Ubuntu ...Missing: organizations | Show results with:organizations
  42. [42]
    Ubuntu Pro | plans and pricing
    Self-Support (software only), With Infra support (24/7), With full support (24/7). Security patching for Ubuntu Main repository for 10 years (esm-infra) ...
  43. [43]
    Visual Studio 2022 Product Lifecycle and Servicing - Microsoft Learn
    Long-Term Servicing Channel (LTSC) support. We realize that sometimes large organizations can't adopt our product updates as quickly as we release them. So, ...Enterprise, Professional... · Long-Term Servicing Channel... · Older Versions Of Visual...<|control11|><|separator|>
  44. [44]
    Wind River Linux LTS Datasheet
    WIND RIVER'S PARTNER ECOSYSTEM. The Wind River partner portfolio includes a large ecosystem of complementary third-party hardware and software solutions.
  45. [45]
    Ubuntu Pro
    Ubuntu Pro. The most comprehensive subscription for open source security and compliance. 30-day trial for enterprises. Always free for personal use.Ubuntu Pro for Devices · Subscription · Pricing · Contact us
  46. [46]
    Ubuntu 14.04 LTS: the cloud platform of choice - Canonical
    Apr 15, 2014 · 14.04 LTS with Icehouse is much anticipated by the OpenStack community as offering the right blend of stability and access to the latest cloud capabilities.<|separator|>
  47. [47]
    Bleeding, Leading, Dull, and Rusting | Blog - Ardalis
    Apr 19, 2024 · Pros: Lower risk than bleeding edge technologies with a stable release. Strong community support and ample learning resources.
  48. [48]
    How Canonical makes money from Ubuntu - CIO
    Mar 16, 2017 · SLES offers maintenance updates for 8-10 years, with extended support for 11-13 years. RHEL is supported for 10 years and then there is extended ...
  49. [49]
    Canonical expands Long Term Support to 12 years starting with ...
    Mar 25, 2024 · Canonical expands Long Term Support for Ubuntu to 12 years starting with Ubuntu 14.04 Trusty Tahr with the new Legacy add-on.<|separator|>
  50. [50]
    Gitflow Workflow | Atlassian Git Tutorial
    Gitflow is an alternative Git branching model that involves the use of feature branches and multiple primary branches.Missing: LTS | Show results with:LTS
  51. [51]
    Patterns for Managing Source Code Branches - Martin Fowler
    Key patterns include Source Branching, Mainline, Healthy Branch, Mainline Integration, Feature Branching, Release Branch, and Release Train.<|control11|><|separator|>
  52. [52]
    Long Term Support releases - Atlassian Documentation
    Jan 27, 2025 · Designate a feature release as a Long Term Support release, at least once every 12 months. · Backport critical security fixes, as outlined in our ...
  53. [53]
    Debian Releases
    The Debian release life cycle encompasses five years: the first three years of full support followed by two years of Long Term Support (LTS). See Debian ...Jessie · Debian “wheezy” Release... · Debian “stretch” Release... · SargeMissing: strategy | Show results with:strategy
  54. [54]
    Containers - Ubuntu
    Explore Ubuntu's trusted container images built from the world's most popular cloud OS. Enjoy long-term support, regular security updates, ...What are container images? · Chiseled Ubuntu · Container Build ServiceMissing: DevOps | Show results with:DevOps
  55. [55]
    Bug Triage: Definition, Examples, and Best Practices - Atlassian
    Bug triage is a process for identifying, tracking, prioritizing, and addressing software bugs. The goal of bug triage is to organize bugs to make them easier ...Missing: maintenance | Show results with:maintenance
  56. [56]
    Securing open source through CVE prioritisation - Ubuntu
    Jul 20, 2023 · This triage process involves assessing every single new publicly announced CVE and determining which (if any) software packages in Ubuntu may be ...
  57. [57]
    Backports - Ubuntu project documentation
    If a package in an Ubuntu release has a bug, it should be fixed either through the Security Update or the Stable Release Updates process, as appropriate. All ...Missing: LTS | Show results with:LTS
  58. [58]
    Canonical reaffirms 10 year LTS of Linux kernel and Ubuntu
    Oct 24, 2023 · We generate a new LTS kernel every two years and maintain it for a total of 10. We provide security updates to the LTS kernels for five years, ...Missing: structures | Show results with:structures<|separator|>
  59. [59]
    Linux Kernel Maintainers Get Some Help from AI - The New Stack
    Jul 4, 2025 · Stable and Long-Term Support (LTS) kernel maintainers usually review around 100 patches per day, every day, including weekends and holidays.
  60. [60]
    Scala development guarantees | The Scala Programming Language
    It is a collaboration between multiple entities (business, nonprofits, individuals) and relies on community contributions as much as the work of its maintainers ...Scala 3 Semantic Versioning · Scala 3 Schedule, Iterations... · Scala 2 Maintenance<|separator|>
  61. [61]
    5 software testing strategies to build into your CI/CD pipeline - Red Hat
    Feb 9, 2022 · This article describes five testing strategies to consider incorporating into your pipeline. Regardless of your CI/CD implementation, introducing these testing ...Missing: LTS protocols
  62. [62]
    What is CI/CD? - Red Hat
    Jun 10, 2025 · CI/CD security is used to safeguard code pipelines with automated checks and testing to prevent vulnerabilities in software delivery.Missing: LTS | Show results with:LTS
  63. [63]
    CI/CD with Jenkins, Git, and Test Driven Development | DO400
    Red Hat DevOps Pipelines and Processes: CI/CD with Jenkins, Git, and Test-Driven Development (TDD) is a practical introduction to DevOps for developers that ...Missing: protocols | Show results with:protocols
  64. [64]
    End-of-life vs. end-of-support vs. moving of repositories - Ask Ubuntu
    Mar 26, 2019 · There is no set date when the archives get moved to old-releases; for 17.04 it occurred within 96 hours as I recall; however usually it's week(s) ...Missing: deprecation notices migration tools
  65. [65]
    Red Hat Enterprise Linux migration process
    Jul 1, 2024 · These migration tools and programs automate many inventory and remediation steps associated with upgrading your subscription or migrating from another Linux ...Missing: LTS notices
  66. [66]
    Git Cherry Pick | Atlassian Git Tutorial
    This new patch commit can be cherry-picked directly to the main branch to fix the bug before it effects more users. Undoing changes and restoring lost ...
  67. [67]
    python/cherry-picker - GitHub
    This tool is used to backport CPython changes from main into one or more of the maintenance branches (eg 3.12, 3.11).
  68. [68]
    Linux package management with YUM and RPM - Red Hat
    Apr 22, 2020 · YUM is the primary package management tool for installing, updating, removing, and managing software packages in Red Hat Enterprise Linux.Missing: LTS cherry- picking
  69. [69]
    Windows 10 Enterprise and Education - Microsoft Lifecycle
    Windows 10 will reach end of support on October 14, 2025. The current version, 22H2, will be the final version of Windows 10.<|separator|>
  70. [70]
    Windows 10 Enterprise LTSC 2019 - Microsoft Lifecycle
    Support Dates ; Windows 10 Enterprise LTSC 2019, 2018-11-13T00:00:00.000-08:00, 2024-01-09T22:59:59.999-08:00 ...
  71. [71]
    Debian 10 Long Term Support reaching end-of-life
    Jun 15, 2024 · Debian 10 buster support will reach its end-of-life on June 30, 2024, nearly five years after its initial release on July 6th, 2019.
  72. [72]
    https://www.becon.de/what-should-i-bear-in-mind-when-changing-the-hardware-on-linux-systems/?lang=en
  73. [73]
    Enterprise Server Market - Share, Trends & Analysis
    Sep 26, 2025 · By operating system, Linux led with 54.87% of enterprise server market share in 2024 and is advancing at a 6.96% CAGR through 2030. By server ...
  74. [74]
    What should I bear in mind when changing the hardware on Linux ...
    Oct 17, 2024 · Changing hardware in a Linux system can be associated with some challenges, as Linux relies heavily on support from the kernel and suitable ...<|separator|>
  75. [75]
    Red Hat Enterprise Linux 10
    Red Hat Enterprise Linux 10 introduces the next era of the operating system (OS), with AI readiness and advanced capabilities to help address the Linux skills ...Missing: LTS | Show results with:LTS
  76. [76]
    Node.js | endoflife.date
    Oct 29, 2025 · LTS release status is “long-term support”, which typically guarantees that critical bugs will be fixed for a total of 30 months.
  77. [77]
    Node.js Releases
    LTS release status is "long-term support", which typically guarantees that critical bugs will be fixed for a total of 30 months. Production applications should ...Node.js v8.17.0 · Index of /download/release... · Latest-gallium · V20.19.5
  78. [78]
    https://endoflife.date/apache-http-server
  79. [79]
    Status of Python versions - Python Developer's Guide
    The main branch is currently the future Python 3.15, and is the only branch that accepts new features. The latest release for each Python version can be found ...Missing: community | Show results with:community
  80. [80]
    Apache HTTP Server | endoflife.date
    Aug 10, 2025 · Check end-of-life, release policy and support schedule for Apache HTTP Server.
  81. [81]
    Apache HTTP Server Version 2.4 Documentation
    The documentation covers topics such as compiling, installing, starting, stopping, run-time configuration, modules, filters, handlers, and server programs.Upgrading to 2.4 from 2.2 · Configuration Files · Getting Started · Module IndexMissing: LTS | Show results with:LTS
  82. [82]
    Introducing MySQL Innovation and Long-Term Support (LTS) versions
    Jul 18, 2023 · 34+ will transition to only bug fixes until 8.0 End-Of-Life (EOL) scheduled for April-2026. Approximately one year from now, MySQL version 8.x ...
  83. [83]
    Microsoft .NET - endoflife.date
    Oct 16, 2025 · LTS releases are supported for three years after the initial release. More information is available on the Microsoft . NET website.
  84. [84]
    Long-term support for Azure Kubernetes Service (AKS) versions
    Aug 28, 2025 · AKS provides a long-term support (LTS) option, which extends the support window for a Kubernetes version to give you more time to plan and test upgrades.
  85. [85]
    Releases · Azure/AKS - GitHub
    Kubernetes version 1.28, 1.29 will become additional Long Term Support (LTS) versions in AKS, alongside existing LTS versions 1.27 and 1.30. AKS Kubernetes ...
  86. [86]
    LTS - Blender
    LTS Releases Currently Maintained ... The last LTS release of the Blender 4.x series, supported until July 2027. ... The first long-term support release in the 4.x ...Blender 4.2 LTSBlender 4.5 LTSBlender 3.6Blender 3.3 LTS2.93 LTS
  87. [87]
    Blender - endoflife.date
    Oct 29, 2025 · LTS releases are supported for 2 years. At first the support level is the same as non-LTS releases; but after the next release is out, they are ...<|control11|><|separator|>
  88. [88]
    Electron | endoflife.date
    The Chromium version of Electron is usually bumped within one or two weeks after a new stable Chromium version gets released. This estimate is not guaranteed ...
  89. [89]
    PyTorch 1.13 release, including beta versions of functorch and ...
    Oct 28, 2022 · Beta includes improved support for Apple M1 chips and functorch, a library that offers composable vmap (vectorization) and autodiff transforms.Missing: LTS | Show results with:LTS
  90. [90]
    Announcing end of support for PyTorch 1.13 starting next release
    Neuron Release 2.21 is the last release to support PyTorch 1.13, its associated Deep Learning Containers (DLCs), and Deep Learning AMIs (DLAMIS) for Trn1, ...
  91. [91]
    Fedora Linux Release Life Cycle
    The Fedora Project releases a new version of Fedora Linux approximately every six months and provides updated packages (maintenance) to these releases for ...Release Dates · Development Process · Development Schedule...
  92. [92]
    LTS Software vs. Regular Releases: Making Informed Choices for ...
    Feb 29, 2024 · Long Term Support, or LTS, refers to a release of a software product that receives bug fixes for an extended period, while newer versions with ...<|control11|><|separator|>
  93. [93]
    Eclipse LTS - Long Term Support | The Eclipse Foundation
    Eclipse LTS enables long term maintenance for Eclipse technologies to help adopters to stay on top of regular software updates to avoid problems upfront.Missing: strategy | Show results with:strategy
  94. [94]
    Eclipse IDE Simultaneous Release
    The Eclipse Foundation and its projects produce a release on a coordinated schedule. This release is often referred to as the Simultaneous Release.
  95. [95]
    Principles - ArchWiki - Arch Linux
    Sep 3, 2025 · It is based on a rolling-release system, which allows a one-time installation with continuous upgrades. Arch Linux incorporates the latest ...Principles · Modernity · Versatility · HistoryMissing: definition | Show results with:definition
  96. [96]
    Portal:Tumbleweed - openSUSE Wiki
    Mar 3, 2020 · The Tumbleweed distribution is a pure rolling release version of openSUSE containing the latest stable versions of all software.
  97. [97]
    Long Term Support vs Rolling Linux Release - Datamation
    Feb 8, 2016 · Obviously there are advantages and disadvantages to using an LTS distro release. That said, when it comes to current software packages, control ...
  98. [98]
    Rolling vs. Fixed release Linux Distros? - GeeksforGeeks
    Oct 10, 2023 · Here, LTS stands for Long Term Support and is basically the most stable and longest supported version of Ubuntu. With a focus on stability ...
  99. [99]
    How to decide between Rolling Releases versus LTS Releases?
    Mar 4, 2017 · A rolling release is newer, with cutting-edge functionality, but potentially more defects. LTS is more stable.Missing: distribution | Show results with:distribution
  100. [100]
    OpenSUSE Tumbleweed: The Stable Rolling Release Linux ...
    Jul 27, 2023 · OpenSUSE Tumbleweed gives you the latest software without the usual pitfalls. The new packages in Tumbleweed undergo thorough SUSE testing, offering stability.
  101. [101]
    Nix channels - NixOS Wiki
    Nix channels are names for verified git commits in Nixpkgs, reified as git branches and disk images. They are categorized as stable or unstable, and large or ...
  102. [102]
    Pinning NixOS with npins, or how to kill channels forever without flakes
    May 20, 2024 · This blog post teaches you how to move your NixOS configuration into a repo wherever you want, and eliminate nix-channel altogether.