Remove LTS from docs

README.md

@@ -174,10 +174,10 @@ number of versions they need to think about), improve search indexing, and help
 us maintain the docs by keeping our build times faster.
 
 In general, we should only version the documentation **when we want to
-concurrently maintain several versions of the docs**, like for major/LTS
-versions. For example - the [Node.js docs](https://nodejs.org/en/docs) are only
-versioned for major releases, like `20.x` and `19.x`. We will adopt this pattern
-as well, and won't have versioned docs for patch or feature releases.
+concurrently maintain several versions of the docs**, like for major versions.
+For example - the [Node.js docs](https://nodejs.org/en/docs) are only versioned
+for major releases, like `20.x` and `19.x`. We will adopt this pattern as well,
+and won't have versioned docs for patch or feature releases.
 
 For additive changes, it should usually be sufficient to indicate which version
 a feature or API was released in. For example - in the Node 20 docs, the

runtime/fundamentals/stability_and_releases.md

@@ -1,6 +1,6 @@
 ---
 title: "Stability and releases"
-description: "Guide to Deno's stability guarantees and release process. Covering release channels, long-term support (LTS), unstable features, versioning policy, and how Deno maintains backward compatibility."
+description: "Guide to Deno's stability guarantees and release process. Covering release channels, unstable features, versioning policy, and how Deno maintains backward compatibility."
 oldUrl:
   - /runtime/manual/runtime/stability/
   - /runtime/fundamentals/stability/
@@ -20,43 +20,15 @@ released.
 
 ### Release channels
 
-Deno offers 4 release channels
+Deno offers 3 release channels
 
 - `stable` - a semver minor/patch release, as described above. This is **the
   default** distribution channel that is recommended for most users.
-- `lts` - long term support for a particular stable release, recommended for
-  enterprise users who prefer not to upgrade so often. See below for details.
 - `rc` - a release candidate for the upcoming semver minor release.
 - `canary` - an unstable release that changes multiple times per day, allows to
   try out latest bug fixes and new features that might end up in the `stable`
   channel.
 
-### Long Term Support (LTS)
-
-Starting with Deno v2.1.0 (released in November 2024), Deno offers an LTS
-(long-term support) channel.
-
-An LTS channel is a minor semver version that we maintain with only
-backwards-compatible bug fixes.
-
-| LTS release version | LTS maintenance start | LTS maintenance end |
-| ------------------- | --------------------- | ------------------- |
-| v2.1                | Feb 1st, 2025         | Apr 30th, 2025      |
-| v2.2                | May 1st, 2025         | Oct 31st, 2025      |
-| v2.4                | Nov 1st, 2025         | Apr 30th, 2026      |
-
-We are initially keeping the LTS support window short while we refine the
-process. **LTS releases occur every six months**, with patch releases as needed
-for bug fixes. We plan to extend this support window to one year in the future.
-
-LTS backports include:
-
-- Security patches
-- Critical bug fixes (e.g., crashes, incorrect computations)
-- **Critical** performance improvements _may_ be backported based on severity.
-
-**API changes and major new features will not be backported.**
-
 ## Unstable APIs
 
 When introducing new APIs, these are first marked as unstable. This means that

runtime/reference/migration_guide.md

@@ -39,16 +39,6 @@ deno.json:
 
 [Read more on `Node.js support` page](/runtime/fundamentals/node/)
 
-### Long Term Support releases
-
-Starting with Deno v2.1.0 (to be released in November 2024) Deno will offer a
-LTS (long-term support) channel.
-
-An LTS version is supported for 6 months, receiving bug fixes and critical
-performance fixes before a new version is promoted to LTS.
-
-[Read more on `Stability and releases` page](/runtime/fundamentals/stability_and_releases/#long-term-support-(lts))
-
 ## Managing dependencies
 
 Deno 2 greatly improves dependency management for npm and JSR packages with