tarantool · AArdeev · Sep 2, 2025 · Sep 2, 2025 · Sep 2, 2025 · Sep 2, 2025
diff --git a/doc/release/_images/releases_calendar_2_x.svg b/doc/release/_images/releases_calendar_2_x.svg
diff --git a/doc/release/calendar.rst b/doc/release/calendar.rst
@@ -1,21 +1,35 @@
 Release calendar
 ================
 
-Every Tarantool release series has :ref:`the same lifecycle <release-series-lifecycle>`.
-To see the lifecycle of Tarantool 2.x versions supported in 2025 see the `calendar <https://www.tarantool.io/en/doc/latest/release/#supported-versions>`_.
+This section contains general information and links to appropriate pages containing details
+about 1.x and 2.x Tarantool releases: release notes, lifecycle information, release policy, and other info.
 
-..  _release-table:
+..  _release-supported-versions:
 
-Release lifetime table
-----------------------
+Supported versions
+------------------
 
-The release lifetime table lists all Tarantool versions
-starting from 1.10.x up to the current latest versions.
-Each link leads to the release notes page of the corresponding version.
-*End of life* means the release series will no longer receive any patches, updates,
-or feature improvements after the specified date.
-*End of support* means that we won't provide technical support to product versions
-after the specified date.
+Every Tarantool release series has :ref:`the same lifecycle <release-series-lifecycle>`
+defined by the release policy. The following diagram visualizes the lifecycle of currently supported Tarantool 2.x versions:
+
+.. image:: _images/releases_calendar_2_x.svg
+    :align: center
+    :alt: Release calendar
+
+.. note::
+
+    *End of life* (*EOL*) means the release series will no longer receive any patches,
+    updates, or feature improvements after the specified date.
+
+    *End of support* (*EOS*) means that we won't provide technical support to product
+    versions after the specified date.
+
+The table below provides information about currently supported versions with links to their
+*What's new* pages in the documentation and/or detailed changelogs on GitHub.
+For information about earlier versions, see :doc:`eos_versions`.
+
+To see the information about Tarantool 3.x versions,
+see the corresponding `page <https://www.tarantool.io/en/doc/latest/release/>`_.
 
 ..  container:: table
 
@@ -109,149 +123,4 @@ after the specified date.
         *   -   :doc:`2.10.0 </release/2.10.0>`
             -   May 22, 2022
             -   September 14, 2023
-            -   December 31, 2025
-
-        *   -   :doc:`2.8.4 </release/2.8.4>`
-            -   April 25, 2022
-            -   April 25, 2022
-            -   December 31, 2024
-
-        *   -   :doc:`2.8.3 </release/2.8.3>`
-            -   December 22, 2021
-            -   April 25, 2022
-            -   December 31, 2024
-
-        *   -   :doc:`2.8.2 </release/2.8.2>`
-            -   August 19, 2021
-            -   April 25, 2022
-            -   December 31, 2024
-
-        *   -   :doc:`2.7.3 </release/2.7.3>`
-            -   August 19, 2021
-            -   August 19, 2021
-            -   August 19, 2021
-
-        *   -   :doc:`2.7.2 </release/2.7.2>`
-            -   April 21, 2021
-            -   August 19, 2021
-            -   August 19, 2021
-
-        *   -   :doc:`2.6.3 </release/2.6.3>`
-            -   April 21, 2021
-            -   April 21, 2021
-            -   April 21, 2021
-
-        *   -   :doc:`2.6.2 </release/2.6.2>`
-            -   December 30, 2020
-            -   April 21, 2021
-            -   April 21, 2021
-
-        *   -   :doc:`2.5.3 </release/2.5.3>`
-            -   December 30, 2020
-            -   December 30, 2020
-            -   December 30, 2020
-
-        *   -   :doc:`2.5.2 </release/2.5.2>`
-            -   October 22, 2020
-            -   December 30, 2020
-            -   December 30, 2020
-
-        *   -   :doc:`2.4.3 </release/2.4.3>`
-            -   October 22, 2020
-            -   October 22, 2020
-            -   October 22, 2020
-
-        *   -   :doc:`2.4.2 </release/2.4.2>`
-            -   July 17, 2020
-            -   October 22, 2020
-            -   October 22, 2020
-
-        *   -   :doc:`2.3.3 </release/2.3.3>`
-            -   July 17, 2020
-            -   July 17, 2020
-            -   July 17, 2020
-
-        *   -   :doc:`2.3.2 </release/2.3.2>`
-            -   April 20, 2020
-            -   July 17, 2020
-            -   July 17, 2020
-
-        *   -   :doc:`2.2.3 </release/2.2.3>`
-            -   April 20, 2020
-            -   April 20, 2020
-            -   April 20, 2020
-
-        *   -   :doc:`2.2.2 </release/2.2.2>`
-            -   December 31, 2019
-            -   April 20, 2020
-            -   April 20, 2020
-
-        *   -   :doc:`1.10.15 LTS </release/1.10.15>`
-            -   February 20, 2023
-            -   February 20, 2023
-            -   February, 2024
-
-        *   -   :doc:`1.10.14 LTS </release/1.10.14>`
-            -   August 8, 2022
-            -   February 20, 2023
-            -   February, 2024
-
-        *   -   :doc:`1.10.13 LTS </release/1.10.13>`
-            -   April 25, 2022
-            -   February 20, 2023
-            -   February, 2024
-
-        *   -   :doc:`1.10.12 LTS </release/1.10.12>`
-            -   December 22, 2021
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.11 LTS </release/1.10.11>`
-            -   August 19, 2021
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.10 LTS </release/1.10.10>`
-            -   April 24, 2021
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.9 LTS </release/1.10.9>`
-            -   December 30, 2020
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.8 LTS </release/1.10.8>`
-            -   October 22, 2020
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.7 LTS </release/1.10.7>`
-            -   July 17, 2020
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.6 LTS </release/1.10.6>`
-            -   April 20, 2020
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :doc:`1.10.5 LTS </release/1.10.5>`
-            -   January 14, 2020
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :ref:`1.10.4 LTS <whats_new_1104>`
-            -   September 26, 2019
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :ref:`1.10.3 LTS <whats_new_1103>`
-            -   April 1, 2019
-            -   February 20, 2022
-            -   February 20, 2023
-
-        *   -   :ref:`1.10.2 LTS <whats_new_1102>`
-            -   October 13, 2018
-            -   February 20, 2022
-            -   February 20, 2023
+            -   December 31, 2025
diff --git a/doc/release/eol_versions.rst → doc/release/eos_versions.rst b/doc/release/eol_versions.rst → doc/release/eos_versions.rst
@@ -1,23 +1,14 @@
 
-EOL versions
+EOS versions
 ============
 
 This page lists release notes for Tarantool versions that have reached
-their end of life in accordance with the :doc:`release policy <policy>`.
+their end of support in accordance with the :doc:`release policy <policy>`.
 See the :doc:`release calendar <calendar>` for more information.
 
 ..  toctree::
     :maxdepth: 1
 
-    2.10.8
-    2.10.7
-    2.10.6
-    2.10.5
-    2.10.4
-    2.10.3
-    2.10.2
-    2.10.1
-    2.10.0
     2.8.4
     2.8.3
     2.8.2

diff --git a/doc/release/index.rst b/doc/release/index.rst
@@ -6,9 +6,11 @@
 Releases
 ========
 
-This section contains release notes for Tarantool versions from 1.6 to 2.11.
+This section contains links to release notes for Tarantool versions from 2.10.0 to 2.11.
+
+For information about earlier release series, see :doc:`EOS Versions <eos_versions>`.
 For information about newer release series, see the corresponding version's
-documentation.
+`documentation <https://www.tarantool.io/en/doc/latest/release/>`_.
 
 To download Tarantool releases, check the `Download <https://www.tarantool.io/en/download/>`_ page.
 
@@ -28,7 +30,16 @@ To learn more, read the :doc:`Compatibility guarantees <compatibility>` article.
     :maxdepth: 1
 
     2.11.0
-    eol_versions
+    2.10.8
+    2.10.7
+    2.10.6
+    2.10.5
+    2.10.4
+    2.10.3
+    2.10.2
+    2.10.1
+    2.10.0
+    eos_versions
 
 ..  toctree::
     :maxdepth: 2

diff --git a/doc/release/legacy-policy.rst b/doc/release/legacy-policy.rst
@@ -1,11 +1,13 @@
 Tarantool legacy release policy
 ===============================
 
+This release policy is actual for Tarantool releases from ``1.6`` and until ``2.8.4`` inclusive.
+Starting from the ``2.10.0`` release, a more actual :doc:`release policy <policy>` is applied.
 
-A Tarantool release is identified by three digits, for example, 2.6.2 or 1.10.9:
+A Tarantool release is identified by three digits, for example, ``2.6.2`` or ``1.10.9``:
 
 *   The first digit stands for a MAJOR release series that introduces
-    some *major changes*. Up to now, there has been only one major release jump
+    some *major changes*. One of major release jumps, for example, has happened
     when we delivered the 2.x release series with the SQL support.
 *   The second digit stands for a MINOR release series that is used for
     introducing new *features*.
@@ -22,14 +24,14 @@ So, each MINOR release series goes through a development-maturity life cycle
 as follows:
 
 1.  **Alpha**. Once a quarter, we start off with a new alpha version,
-    such as 2.3.0, 2.4.0, and so on. This is not what an alpha release usually
+    such as ``2.3.0``, ``2.4.0``, and so on. This is not what an alpha release usually
     means in the typical software release life cycle but rather the current trunk
     version which is under heavy development and can be unstable.
     The current alpha version always lives in the master branch.
 
 2.  **Beta**. When all the features planned are implemented, we fork a new branch
     from the master branch and tag it as a new beta version.
-    It contains ``1`` for the PATCH digit, e.g., 2.3.1, 2.4.1, and so on.
+    It contains ``1`` for the PATCH digit, e.g., ``2.3.1``, ``2.4.1``, and so on.
     This version cannot be called stable yet (feature freeze has just been done)
     although there are no known critical regressions in it since
     the last stable release.
@@ -38,11 +40,11 @@ as follows:
     Finally, after we see our beta version runs successfully in
     a production or development environment during another quarter while we fix
     incoming bugs, we declare this version stable. It is tagged with ``2`` for
-    the PATCH digit, e.g., 2.3.2, 2.4.2, and so on.
+    the PATCH digit, e.g., ``2.3.2``, ``2.4.2``, and so on.
 
     We support such version for 3 months while making another stable release
     by fixing all bugs found. We release it in a quarter. This last tag
-    contains ``3`` for the PATCH digit, e.g., 2.3.3, 2.4.3, and so on.
+    contains ``3`` for the PATCH digit, e.g., ``2.3.3``, ``2.4.3``, and so on.
     After the tag is set, no new changes are allowed to the release branch,
     and it is declared deprecated and superseded by a newer MINOR version.
 
@@ -54,7 +56,7 @@ release series:
 
 *   **LTS (Long Term Support)** is a release series that is supported
     for 3 years (community) and up to 5 years (paying customers).
-    Current LTS release series is 1.10, and it receives only PATCH level
+    Current LTS release series is ``1.10``, and it receives only PATCH level
     releases.
 
 *   **Standard** is a release series that is supported only for a few months
@@ -92,14 +94,14 @@ by an example of some latest releases and release series:
 *Support* means that we continue fixing bugs. We add bug fixes simultaneously
 into the following release series: LTS, last stable, beta, and alpha.
 If we look at the release diagram above, it means that the bug fixes are to be
-added into 1.10, 2.4, 2.5, and 2.6 release series.
+added into ``1.10``, ``2.4``, ``2.5``, and ``2.6`` release series.
 
 To sum it up, once a quarter we release (see the release diagram above for
 reference):
 
-*   next LTS release, e.g., 1.10.9
-*   two stable releases, e.g., 2.5.3 and 2.6.2
-*   beta version of the next release series, e.g., 2.7.1.
+*   next LTS release, e.g., ``1.10.9``
+*   two stable releases, e.g., ``2.5.3`` and ``2.6.2``
+*   beta version of the next release series, e.g., ``2.7.1.``
 
 In all supported releases, when we find and fix an outstanding CVE/vulnerability,
 we deliver a patch for that but do not tag a new PATCH level version.