Skip to content

Commit 633dfaf

Browse files
authored
Adds timeless approach to release page (#5235)
* Adds timeless approach to release page * Adds description of EOS concept to the release page * Fixes #4065
1 parent 5ccdb23 commit 633dfaf

File tree

1 file changed

+19
-10
lines changed

1 file changed

+19
-10
lines changed

doc/release/policy.rst

Lines changed: 19 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -6,19 +6,19 @@ Tarantool release policy
66
Summary
77
-------
88

9-
The Tarantool release policy is changing to become more clear and intuitive.
10-
The new policy uses a `SemVer-like <https://semver.org/>`__ versioning format,
11-
and introduces a new version lifecycle with more long-time support series.
12-
This document explains the new release policy, versioning rules, and :term:`release series` lifecycle.
9+
The Tarantool release policy is constantly changing to become more clear and intuitive.
10+
The stated policy uses a `SemVer-like <https://semver.org/>`__ versioning format,
11+
and upholds version lifecycle with more long-time support series.
12+
This document explains the Tarantool release policy, versioning rules, and :term:`release series` lifecycle.
1313

14-
The new release policy replaces :doc:`the legacy policy </release/legacy-policy>`
14+
The stated release policy replaces :doc:`the legacy policy </release/legacy-policy>`
1515
for:
1616

1717
* The ``2.x.y`` series since the ``2.10.0`` release.
18-
Development for this new release starts with version ``2.10.0-beta1``.
19-
* The future ``3.0.0`` series.
18+
Development for this release starts with version ``2.10.0-beta1``.
19+
* The ``3.0.0`` series.
2020

21-
Here are the most significant changes from the legacy release policy:
21+
Here are the most significant changes from the previously supported legacy release policy:
2222

2323
* The third number in the version label doesn't distinguish between
2424
pre-release (alpha and beta) and release versions.
@@ -29,15 +29,15 @@ Here are the most significant changes from the legacy release policy:
2929
while ``2.x.y`` had stable releases, but wasn't an LTS series.
3030
Now both series are long-term supported.
3131

32-
The topics below describe the new versioning policy in more detail.
32+
The topics below describe the versioning policy in more detail.
3333

3434
Versioning policy
3535
-----------------
3636

3737
Release series and versions
3838
~~~~~~~~~~~~~~~~~~~~~~~~~~~
3939

40-
The new Tarantool release policy is based on having several release series,
40+
The Tarantool release policy is based on having several release series,
4141
each with its own lifecycle, pre-release and release versions.
4242

4343
.. glossary::
@@ -265,6 +265,15 @@ that reaches EOL.
265265
A release series cannot reach EOL until the vast majority of production environments,
266266
for which we have commitments and SLAs, is updated to a newer series.
267267

268+
End of support
269+
~~~~~~~~~~~~~~~~~
270+
271+
The end of support (EOS) date is later in time than the EOL date. When the series
272+
reaches EOS, the Tarantool team ceases its technical support and does not comply with support-
273+
related inquiries.
274+
275+
It is recommended that the customers follow the :ref:`calendar <release-supported-versions>`
276+
and plan for updates of their Tarantool version before the EOS date.
268277

269278
Versions per lifecycle stage
270279
----------------------------

0 commit comments

Comments
 (0)