From edb43389a21b18e65ac684bf37f5a0ea1b24a700 Mon Sep 17 00:00:00 2001 From: "a.ardeev" Date: Tue, 8 Jul 2025 14:56:55 +0300 Subject: [PATCH 1/3] Adds timeless approach to release page Adds description of EOS concept to the release page Fixes #4065 --- doc/release/policy.rst | 29 +++++++++++++++++++---------- 1 file changed, 19 insertions(+), 10 deletions(-) diff --git a/doc/release/policy.rst b/doc/release/policy.rst index fe5d451ca7..5ae68a1885 100644 --- a/doc/release/policy.rst +++ b/doc/release/policy.rst @@ -6,19 +6,19 @@ Tarantool release policy Summary ------- -The Tarantool release policy is changing to become more clear and intuitive. -The new policy uses a `SemVer-like `__ versioning format, -and introduces a new version lifecycle with more long-time support series. -This document explains the new release policy, versioning rules, and :term:`release series` lifecycle. +The Tarantool release policy is constantly changing to become more clear and intuitive. +The stated policy uses a `SemVer-like `__ versioning format, +and upholds version lifecycle with more long-time support series. +This document explains the Tarantool release policy, versioning rules, and :term:`release series` lifecycle. -The new release policy replaces :doc:`the legacy policy ` +The stated release policy replaces :doc:`the legacy policy ` for: * The ``2.x.y`` series since the ``2.10.0`` release. - Development for this new release starts with version ``2.10.0-beta1``. -* The future ``3.0.0`` series. + Development for this release starts with version ``2.10.0-beta1``. +* The ``3.0.0`` series. -Here are the most significant changes from the legacy release policy: +Here are the most significant changes from the previously supported legacy release policy: * The third number in the version label doesn't distinguish between pre-release (alpha and beta) and release versions. @@ -29,7 +29,7 @@ Here are the most significant changes from the legacy release policy: while ``2.x.y`` had stable releases, but wasn't an LTS series. Now both series are long-term supported. -The topics below describe the new versioning policy in more detail. +The topics below describe the versioning policy in more detail. Versioning policy ----------------- @@ -37,7 +37,7 @@ Versioning policy Release series and versions ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The new Tarantool release policy is based on having several release series, +The Tarantool release policy is based on having several release series, each with its own lifecycle, pre-release and release versions. .. glossary:: @@ -265,6 +265,15 @@ that reaches EOL. A release series cannot reach EOL until the vast majority of production environments, for which we have commitments and SLAs, is updated to a newer series. +End of support +--------------- + +The end of support (EOS) date is later in time than the EOL date. When the series +reaches EOS, the Tarantool team ceases its support and does not comply with support- +related inquiries. + +It is recommended that the customers follow the :doc:`Supported versions <_release-supported-versions>` +calendar and plan for updates of their Tarantool version before the EOS date. Versions per lifecycle stage ---------------------------- From c5b1ea32be36d53c7c2df3aae131d9996eefe617 Mon Sep 17 00:00:00 2001 From: "a.ardeev" Date: Tue, 8 Jul 2025 15:32:14 +0300 Subject: [PATCH 2/3] Fixes syntax --- doc/release/policy.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/release/policy.rst b/doc/release/policy.rst index 5ae68a1885..ea85d5a2f3 100644 --- a/doc/release/policy.rst +++ b/doc/release/policy.rst @@ -266,13 +266,13 @@ A release series cannot reach EOL until the vast majority of production environm for which we have commitments and SLAs, is updated to a newer series. End of support ---------------- +-------------- The end of support (EOS) date is later in time than the EOL date. When the series -reaches EOS, the Tarantool team ceases its support and does not comply with support- +reaches EOS, the Tarantool team ceases its technical support and does not comply with support- related inquiries. -It is recommended that the customers follow the :doc:`Supported versions <_release-supported-versions>` +It is recommended that the customers follow the :ref:`Supported versions <_release-supported-versions>` calendar and plan for updates of their Tarantool version before the EOS date. Versions per lifecycle stage From 7e79aa09f67eecbea660065cc11fda67826686f1 Mon Sep 17 00:00:00 2001 From: "a.ardeev" Date: Tue, 8 Jul 2025 15:45:42 +0300 Subject: [PATCH 3/3] Ref and heading issue --- doc/release/policy.rst | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/doc/release/policy.rst b/doc/release/policy.rst index ea85d5a2f3..7da2942338 100644 --- a/doc/release/policy.rst +++ b/doc/release/policy.rst @@ -266,14 +266,14 @@ A release series cannot reach EOL until the vast majority of production environm for which we have commitments and SLAs, is updated to a newer series. End of support --------------- +~~~~~~~~~~~~~~~~~ The end of support (EOS) date is later in time than the EOL date. When the series reaches EOS, the Tarantool team ceases its technical support and does not comply with support- related inquiries. -It is recommended that the customers follow the :ref:`Supported versions <_release-supported-versions>` -calendar and plan for updates of their Tarantool version before the EOS date. +It is recommended that the customers follow the :ref:`calendar ` +and plan for updates of their Tarantool version before the EOS date. Versions per lifecycle stage ----------------------------