redis · rrelledge · Dec 11, 2025 · Dec 11, 2025 · Dec 11, 2025
diff --git a/content/embeds/rs-upgrade-paths.md b/content/embeds/rs-upgrade-paths.md
@@ -1,5 +1,3 @@
-## Supported upgrade paths
-
 <span title="Check mark icon">&#x2705;</span> Supported – You can upgrade directly from the current Redis Software cluster version.
 
 <span title="X icon">:x:</span> Not supported – You cannot upgrade directly from the current Redis Software cluster version. You must first upgrade to a supported intermediate version.

diff --git a/content/operate/rs/7.22/installing-upgrading/product-lifecycle.md b/content/operate/rs/7.22/installing-upgrading/product-lifecycle.md
@@ -11,7 +11,7 @@ weight: 100
 tocEmbedHeaders: true
 url: '/operate/rs/7.22/installing-upgrading/product-lifecycle/'
 ---
-The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.com/software-subscription-agreement).
+The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.io/legal/software-agreement/).
 However, for any discrepancy between the two policies, the subscription agreement prevails.
 
 Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle" >}}).
@@ -52,6 +52,8 @@ This update to the EOL policy allows a lead time of at least 24 months to upgrad
 | 5.4 – December 2018                       | December 31, 2020  |
 | 5.2 – June 2018                           | December 31, 2019  |
 
+## Supported cluster version upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 For detailed upgrade instructions, see [Upgrade a Redis Enterprise Software cluster]({{<relref "/operate/rs/7.22/installing-upgrading/upgrading/upgrade-cluster">}}).

diff --git a/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-cluster.md b/content/operate/rs/7.22/installing-upgrading/upgrading/upgrade-cluster.md
@@ -21,6 +21,8 @@ To upgrade a cluster's Redis Software version, use one of the following methods:
 
 - [Rolling upgrade](#rolling-upgrade) - Minimize downtime by adding new nodes with an updated Redis Software version to the cluster, one at a time, while keeping the rest of the cluster operational. This method is recommended for production environments that require continuous availability.
 
+## Supported upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 See the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/7.22/installing-upgrading/product-lifecycle">}}) for more information about release numbers and the end-of-life schedule.

diff --git a/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md b/content/operate/rs/7.4/installing-upgrading/product-lifecycle.md
@@ -11,7 +11,7 @@ weight: 100
 tocEmbedHeaders: true
 url: '/operate/rs/7.4/installing-upgrading/product-lifecycle/'
 ---
-The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.com/software-subscription-agreement).
+The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.io/legal/software-agreement/).
 However, for any discrepancy between the two policies, the subscription agreement prevails.
 
 Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle" >}}).
@@ -50,6 +50,8 @@ This update to the EOL policy allows a lead time of at least 24 months to upgrad
 | 5.4 – December 2018                       | December 31, 2020  |
 | 5.2 – June 2018                           | December 31, 2019  |
 
+## Supported cluster version upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 For detailed upgrade instructions, see [Upgrade a Redis Enterprise Software cluster]({{<relref "/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster">}}).
diff --git a/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster.md b/content/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster.md
@@ -13,6 +13,8 @@ tocEmbedHeaders: true
 url: '/operate/rs/7.4/installing-upgrading/upgrading/upgrade-cluster/'
 ---
 
+## Supported upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 See the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/7.4/installing-upgrading/product-lifecycle">}}) for more information about release numbers and the end-of-life schedule.

diff --git a/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md b/content/operate/rs/7.8/installing-upgrading/product-lifecycle.md
@@ -11,7 +11,7 @@ weight: 100
 tocEmbedHeaders: true
 url: '/operate/rs/7.8/installing-upgrading/product-lifecycle/'
 ---
-The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.com/software-subscription-agreement).
+The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.io/legal/software-agreement/).
 However, for any discrepancy between the two policies, the subscription agreement prevails.
 
 Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle" >}}).
@@ -51,6 +51,8 @@ This update to the EOL policy allows a lead time of at least 24 months to upgrad
 | 5.4 – December 2018                       | December 31, 2020  |
 | 5.2 – June 2018                           | December 31, 2019  |
 
+## Supported cluster version upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 For detailed upgrade instructions, see [Upgrade a Redis Enterprise Software cluster]({{<relref "/operate/rs/7.8/installing-upgrading/upgrading/upgrade-cluster">}}).

diff --git a/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-cluster.md b/content/operate/rs/7.8/installing-upgrading/upgrading/upgrade-cluster.md
@@ -21,6 +21,8 @@ To upgrade a cluster's Redis Software version, use one of the following methods:
 
 - [Rolling upgrade](#rolling-upgrade) - Minimize downtime by adding new nodes with an updated Redis Software version to the cluster, one at a time, while keeping the rest of the cluster operational. This method is recommended for production environments that require continuous availability.
 
+## Supported upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 See the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/7.8/installing-upgrading/product-lifecycle">}}) for more information about release numbers and the end-of-life schedule.

diff --git a/content/operate/rs/installing-upgrading/product-lifecycle.md b/content/operate/rs/installing-upgrading/product-lifecycle.md
@@ -5,19 +5,23 @@ categories:
 - docs
 - operate
 - rs
-description: The product lifecycle of Redis Enterprise Software.
+description: The product lifecycle of Redis Enterprise Software cluster versions and bundled Redis database versions.
 linkTitle: Product lifecycle
 weight: 100
 tocEmbedHeaders: true
 ---
-The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.com/software-subscription-agreement).
+The Redis Enterprise Software product lifecycle fully reflects the [subscription agreement](https://redis.io/legal/software-agreement/).
 However, for any discrepancy between the two policies, the subscription agreement prevails.
 
 Redis Enterprise modules follow the [modules lifecycle]({{< relref "/operate/oss_and_stack/stack-with-enterprise/modules-lifecycle" >}}).
 
-## Release numbers
+## Redis Enterprise Software cluster version lifecycle
 
-Redis uses a four-place numbering scheme to designate released versions of its products.
+This section describes the lifecycle policy for Redis Enterprise Software cluster versions.
+
+### Cluster version release numbers
+
+Redis Enterprise Software uses a four-place numbering scheme to designate released cluster versions.
 The format is "Major1.Major2.Minor-Build".
 
 - Major sections of the version number represents fundamental changes and additions in
@@ -32,10 +36,10 @@ The format is "Major1.Major2.Minor-Build".
 Redis Enterprise Software typically gets two major releases every year but the product shipping cycles may vary.
 Maintenance releases, typically available on the last minor release of the current major1.major2 release are typically made available on a monthly cadence, although cycles may vary.
 
-## End-of-life schedule {#endoflife-schedule}
+### Cluster version end-of-life schedule {#endoflife-schedule}
 
-For Redis Enterprise Software versions 6.2 and later, the end-of-life (EOL) for each major release occurs 24 months after the formal release of the subsequent major version. Monthly maintenance will be provided on the last minor release of the major1.major2 releases.
-This update to the EOL policy allows a lead time of at least 24 months to upgrade to the new release after it is available.
+For Redis Enterprise Software cluster versions 6.2 and later, the end-of-life (EOL) for each major release occurs 24 months after the formal release of the subsequent major version. Monthly maintenance will be provided on the last minor release of the major1.major2 releases.
+This update to the EOL policy allows a lead time of at least 24 months to upgrade to the new cluster version after it is available.
 
 
 | Version - Release date | End of Life (EOL)  |
@@ -52,10 +56,71 @@ This update to the EOL policy allows a lead time of at least 24 months to upgrad
 | 5.4 – December 2018                       | December 31, 2020  |
 | 5.2 – June 2018                           | December 31, 2019  |
 
+The following timeline chart visualizes the Redis Enterprise Software product lifecycle, showing release dates and end-of-life dates for each major version:
+
+```timeline {title="Redis Enterprise Software product lifecycle"}
+8.0: Oct 2025 - TBD
+7.22: May 2025 - Oct 30, 2027
+7.8: Nov 2024 - May 30, 2027
+7.4: Feb 2024 - Nov 30, 2026
+7.2: Aug 2023 - Feb 28, 2026
+6.4: Feb 2023 - Aug 31, 2025
+6.2: Aug 2021 - Feb 28, 2025
+6.0: May 2020 - May 31, 2022
+5.6: Apr 2020 - Oct 31, 2021
+5.4: Dec 2018 - Dec 31, 2020
+5.2: June 2018 - Dec 31, 2019
+```
+
+### Supported cluster version upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 For detailed upgrade instructions, see [Upgrade a Redis Enterprise Software cluster]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-cluster">}}).
 
 {{<note>}}
 Redis Enterprise for Kubernetes has its own support lifecycle, which accounts for the Kubernetes distribution lifecycle. For details, see [Supported Kubernetes distributions]({{<relref "/operate/kubernetes/reference/supported_k8s_distributions">}}).
 {{</note>}}
+
+## Redis database version management
+
+The following sections describe the lifecycle policy for Redis database versions bundled with Redis Enterprise Software.
+
+### Redis database version structure
+
+Redis database versions use a **MAJOR.MINOR.PATCH** versioning scheme:
+
+- **Major versions**: Significant changes that may include breaking changes (for example, Redis 7 → Redis 8)
+
+- **Minor versions**: New features and improvements within a major version (for example, 8.2 → 8.4 → 8.6)
+
+- **Patch versions**: Bug fixes and security updates (for example, 8.2.1 → 8.2.2)
+
+### Redis database version support policy
+
+As of Redis Enterprise Software version 8.0.x, Redis database versions follow a long-term and short-term support model as follows:
+
+- **Long-term support**: The first minor release and last minor release of each major database version receive extended support of 5 years.
+
+- **Short-term support**: Minor versions between the first minor release and last minor release receive short-term support of 6 months.
+
+For example:
+
+| Redis DB version | Release type | Support type |
+|------------------|--------------|--------------|
+| 8.0 | Major release | Short-term |
+| 8.2 | First minor release | Long-term |
+| 8.x | Intermediate minor release | Short-term |
+| 8.z | Last minor release | Long-term |
+
+Redis database versions have the following end-of-life dates:
+
+| Redis version | End-of-life (EOL) |
+|---------------|-------------------|
+| **Redis 8.2** | TBD |
+| **Redis 8.0** | TBD |
+| **Redis 7.4** | December 1, 2029 |
+| **Redis 7.2** | December 1, 2029 |
+| **Redis 6.2** | April 1, 2027 |
+
+For detailed database upgrade instructions, see [Upgrade a Redis Enterprise Software database]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-database">}}) or [Upgrade an Active-Active database]({{<relref "/operate/rs/installing-upgrading/upgrading/upgrade-active-active">}}).
diff --git a/content/operate/rs/installing-upgrading/upgrading/upgrade-cluster.md b/content/operate/rs/installing-upgrading/upgrading/upgrade-cluster.md
@@ -20,6 +20,8 @@ To upgrade a cluster's Redis Software version, use one of the following methods:
 
 - [Rolling upgrade](#rolling-upgrade) - Minimize downtime by adding new nodes with an updated Redis Software version to the cluster, one at a time, while keeping the rest of the cluster operational. This method is recommended for production environments that require continuous availability.
 
+## Supported upgrade paths
+
 {{<embed-md "rs-upgrade-paths.md">}}
 
 See the [Redis Enterprise Software product lifecycle]({{<relref "/operate/rs/installing-upgrading/product-lifecycle">}}) for more information about release numbers and the end-of-life schedule.

diff --git a/layouts/_default/_markup/render-codeblock-timeline.html b/layouts/_default/_markup/render-codeblock-timeline.html
@@ -0,0 +1,14 @@
+{{ $width := (index .Attributes "width") | default "100%" }}
+{{ $title := (index .Attributes "title") | default "Timeline" }}
+
+<div class="timeline-container" style="width: {{ $width }};">
+  <pre class="timeline-source" 
+       data-timeline-title="{{ $title }}" 
+       style="display: none;">{{ .Inner | htmlEscape }}</pre>
+  <div class="timeline-fallback">
+    <h4>{{ $title }}</h4>
+    <pre style="background-color: #f8f9fa; padding: 1rem; border-radius: 0.5rem; font-family: 'Space Mono', monospace; font-size: 12px;">{{ .Inner | htmlEscape }}</pre>
+  </div>
+</div>
+
+{{ .Page.Store.Set "hasTimeline" true }}
diff --git a/layouts/_default/baseof.html b/layouts/_default/baseof.html
@@ -114,5 +114,10 @@
     {{ if .Page.Store.Get "hasDecisionTree" }}
     <script src="{{ "js/decision-tree.js" | relURL }}"></script>
     {{ end }}
+
+    <!-- Timeline functionality -->
+    {{ if .Page.Store.Get "hasTimeline" }}
+    <script src="{{ "js/timeline.js" | relURL }}"></script>
+    {{ end }}
   </body>
 </html>