@@ -6,19 +6,19 @@ Tarantool release policy
6
6
Summary
7
7
-------
8
8
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.
13
13
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 >`
15
15
for:
16
16
17
17
* 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.
20
20
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:
22
22
23
23
* The third number in the version label doesn't distinguish between
24
24
pre-release (alpha and beta) and release versions.
@@ -29,15 +29,15 @@ Here are the most significant changes from the legacy release policy:
29
29
while ``2.x.y `` had stable releases, but wasn't an LTS series.
30
30
Now both series are long-term supported.
31
31
32
- The topics below describe the new versioning policy in more detail.
32
+ The topics below describe the versioning policy in more detail.
33
33
34
34
Versioning policy
35
35
-----------------
36
36
37
37
Release series and versions
38
38
~~~~~~~~~~~~~~~~~~~~~~~~~~~
39
39
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,
41
41
each with its own lifecycle, pre-release and release versions.
42
42
43
43
.. glossary ::
@@ -265,6 +265,15 @@ that reaches EOL.
265
265
A release series cannot reach EOL until the vast majority of production environments,
266
266
for which we have commitments and SLAs, is updated to a newer series.
267
267
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.
268
277
269
278
Versions per lifecycle stage
270
279
----------------------------
0 commit comments