Skip to content

Adds timeless approach to release page #5235

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jul 9, 2025
Merged

Adds timeless approach to release page #5235

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
edb4338
Adds timeless approach to release page
AArdeev Jul 8, 2025
c5b1ea3
Fixes syntax
AArdeev Jul 8, 2025
7e79aa0
Ref and heading issue
AArdeev Jul 8, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
29 changes: 19 additions & 10 deletions doc/release/policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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 <https://semver.org/>`__ 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 <https://semver.org/>`__ 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 </release/legacy-policy>`
The stated release policy replaces :doc:`the legacy policy </release/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.
Expand All @@ -29,15 +29,15 @@ 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
-----------------

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::
Expand Down Expand Up @@ -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 technical support and does not comply with support-
related inquiries.

It is recommended that the customers follow the :ref:`calendar <release-supported-versions>`
and plan for updates of their Tarantool version before the EOS date.

Versions per lifecycle stage
----------------------------
Expand Down