Skip to content

Commit a402c9d

Browse files
committed
Removes outdated info from Release Policy (refernce to legacy release policy)
Fixes #5281
1 parent aac84bc commit a402c9d

File tree

1 file changed

+0
-20
lines changed

1 file changed

+0
-20
lines changed

doc/release/policy.rst

Lines changed: 0 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -11,26 +11,6 @@ The stated policy uses a `SemVer-like <https://semver.org/>`__ versioning format
1111
and upholds version lifecycle with more long-time support series.
1212
This document explains the Tarantool release policy, versioning rules, and :term:`release series` lifecycle.
1313

14-
The stated release policy replaces :doc:`the legacy policy </release/legacy-policy>`
15-
for:
16-
17-
* The ``2.x.y`` series since the ``2.10.0`` release.
18-
Development for this release starts with version ``2.10.0-beta1``.
19-
* The ``3.0.0`` series.
20-
21-
Here are the most significant changes from the previously supported legacy release policy:
22-
23-
* The third number in the version label doesn't distinguish between
24-
pre-release (alpha and beta) and release versions.
25-
Instead, it is used for patch (bugfix-only) releases.
26-
Pre-release versions have suffixes, like ``3.0.0-alpha1``.
27-
28-
* In the legacy release policy, ``1.10`` was a long-term support (LTS) series,
29-
while ``2.x.y`` had stable releases, but wasn't an LTS series.
30-
Now both series are long-term supported.
31-
32-
The topics below describe the versioning policy in more detail.
33-
3414
Versioning policy
3515
-----------------
3616

0 commit comments

Comments
 (0)