Skip to content

2.11 calendar and release information update #5340

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

Open
wants to merge 9 commits into
base: 2.11
Choose a base branch
from
Open

2.11 calendar and release information update #5340

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
a38ceb1
Limits calendar in "2.11" with 2026.
AArdeev Sep 2, 2025
b3d2472
Adds link to latest
AArdeev Sep 2, 2025
c95dec2
Rewrites the calendar page to make it consistent with the latest version
AArdeev Sep 2, 2025
6169d5d
Release page and EOL page rewritten
AArdeev Sep 2, 2025
8122dff
Minor fix
AArdeev Sep 2, 2025
44210b8
Updates Release Policy and Legacy release policy
AArdeev Sep 3, 2025
5a751e5
Fix wording for push
AArdeev Nov 10, 2025
4cd1c8a
Fix by comments
AArdeev Nov 14, 2025
ae9ba8d
Adds info on 2.11.8 to calendar
AArdeev Nov 14, 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
4 changes: 4 additions & 0 deletions doc/release/_images/releases_calendar_2_x.svg
View file
Open in desktop
Copy link

@sergos sergos Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need to update the picture: latest release is 2.11.8

Copy link
Contributor Author

@AArdeev AArdeev Nov 13, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please share EOL /EOS dates for 2.11.8?

Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
193 changes: 34 additions & 159 deletions doc/release/calendar.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,21 +1,36 @@
Release calendar
================

Every Tarantool release series has :ref:`the same lifecycle <release-series-lifecycle>`.
To see the lifecycle of Tarantool 2.x versions supported in 2025 see the `calendar <https://www.tarantool.io/en/doc/latest/release/#supported-versions>`_.
This section contains general information and links to appropriate pages containing details
about 1.x and 2.x Tarantool releases: release notes, lifecycle information, release policy, and other info.

.. _release-table:
.. _release-supported-versions:

Release lifetime table
----------------------
Supported versions
------------------

The release lifetime table lists all Tarantool versions
starting from 1.10.x up to the current latest versions.
Each link leads to the release notes page of the corresponding version.
*End of life* means the release series will no longer receive any patches, updates,
or feature improvements after the specified date.
*End of support* means that we won't provide technical support to product versions
after the specified date.
Every Tarantool release series has the same :ref:`lifecycle <release-series-lifecycle>`
defined by the release policy. The following diagram visualizes the lifecycle of currently supported Tarantool 2.x versions:

.. image:: _images/releases_calendar_2_x.svg
:align: center
:alt: Release calendar

.. note::

*End of life* (*EOL*) means the release series will no longer receive any automatic patches,
updates, or feature improvements after the specified date. However, periodic patches containing
critical or vulnerability fixes may still be delivered.

*End of support* (*EOS*) means that we won't provide technical support to product
versions after the specified date.

The table below provides information about currently supported versions with links to their
*What's new* pages in the documentation and/or detailed changelogs on GitHub.
For information about earlier versions, see :doc:`eos_versions`.

To see the information about Tarantool 3.x versions,
see the corresponding `page <https://www.tarantool.io/en/doc/latest/release/>`_.

.. container:: table

Copy link
Contributor

@sergepetrenko sergepetrenko Nov 14, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

End of life for 2.11.7 is May 24, 2025 while its release date is May 29, 2025 - that looks strange :)

Also I don't see the reason to put separate end of life badges on patch releases, like 2.11.6 or 2.11.7, technically, 2.11.7 will never receive any fixes: there won't be another 2.11.7-smth release with a fixed vulnerability. That fix would be in 2.11.8. So IMO End of life should apply to the release series as a whole. Like, 2.11 series should have a single 'End of life'.

At the same time it's probably good to specify End of support per patch release. Like, 2.11.1 has End of support planned for 2024, and 2.11.8 has End of support in 2027. These are not real dates, just a suggestion.

Copy link
Contributor Author

@AArdeev AArdeev Nov 14, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Great suggestion, where to get actual dates from? (i put a "not planned yet" EOL/EOS for 2.11.8 for now)

Copy link
Contributor

@sergepetrenko sergepetrenko Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

AFAIU EOL for 2.11 series has already happened, and it's May 29, 2025 - the date of the last regular 2.11 release.
@sergos, @Galiev-Ruslan - is this right?

My suggestion is to drop separate EOL entries per each release (they're already the same for 2.11.1 - 2.11.6) and state that EOL for the 2.11.* series as a whole is May 29, 2025.

Speaking of EOS dates I'm not sure. "Not planned yet" for all 2.11.* releases, probably?

Expand All @@ -26,9 +41,14 @@ after the specified date.
- End of life
- End of support

* - `2.11.8 LTS <https://github.com/tarantool/tarantool/releases/tag/2.11.8>`_
- October 15, 2025
- Not planned yet
- Not planned yet

* - `2.11.7 LTS <https://github.com/tarantool/tarantool/releases/tag/2.11.7>`_
- May 29, 2025
- May 24, 2025
- May 29, 2025
- Not planned yet

* - `2.11.6 LTS <https://github.com/tarantool/tarantool/releases/tag/2.11.6>`_
Expand Down Expand Up @@ -109,149 +129,4 @@ after the specified date.
* - :doc:`2.10.0 </release/2.10.0>`
- May 22, 2022
- September 14, 2023
- December 31, 2025

* - :doc:`2.8.4 </release/2.8.4>`
- April 25, 2022
- April 25, 2022
- December 31, 2024

* - :doc:`2.8.3 </release/2.8.3>`
- December 22, 2021
- April 25, 2022
- December 31, 2024

* - :doc:`2.8.2 </release/2.8.2>`
- August 19, 2021
- April 25, 2022
- December 31, 2024

* - :doc:`2.7.3 </release/2.7.3>`
- August 19, 2021
- August 19, 2021
- August 19, 2021

* - :doc:`2.7.2 </release/2.7.2>`
- April 21, 2021
- August 19, 2021
- August 19, 2021

* - :doc:`2.6.3 </release/2.6.3>`
- April 21, 2021
- April 21, 2021
- April 21, 2021

* - :doc:`2.6.2 </release/2.6.2>`
- December 30, 2020
- April 21, 2021
- April 21, 2021

* - :doc:`2.5.3 </release/2.5.3>`
- December 30, 2020
- December 30, 2020
- December 30, 2020

* - :doc:`2.5.2 </release/2.5.2>`
- October 22, 2020
- December 30, 2020
- December 30, 2020

* - :doc:`2.4.3 </release/2.4.3>`
- October 22, 2020
- October 22, 2020
- October 22, 2020

* - :doc:`2.4.2 </release/2.4.2>`
- July 17, 2020
- October 22, 2020
- October 22, 2020

* - :doc:`2.3.3 </release/2.3.3>`
- July 17, 2020
- July 17, 2020
- July 17, 2020

* - :doc:`2.3.2 </release/2.3.2>`
- April 20, 2020
- July 17, 2020
- July 17, 2020

* - :doc:`2.2.3 </release/2.2.3>`
- April 20, 2020
- April 20, 2020
- April 20, 2020

* - :doc:`2.2.2 </release/2.2.2>`
- December 31, 2019
- April 20, 2020
- April 20, 2020

* - :doc:`1.10.15 LTS </release/1.10.15>`
- February 20, 2023
- February 20, 2023
- February, 2024

* - :doc:`1.10.14 LTS </release/1.10.14>`
- August 8, 2022
- February 20, 2023
- February, 2024

* - :doc:`1.10.13 LTS </release/1.10.13>`
- April 25, 2022
- February 20, 2023
- February, 2024

* - :doc:`1.10.12 LTS </release/1.10.12>`
- December 22, 2021
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.11 LTS </release/1.10.11>`
- August 19, 2021
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.10 LTS </release/1.10.10>`
- April 24, 2021
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.9 LTS </release/1.10.9>`
- December 30, 2020
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.8 LTS </release/1.10.8>`
- October 22, 2020
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.7 LTS </release/1.10.7>`
- July 17, 2020
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.6 LTS </release/1.10.6>`
- April 20, 2020
- February 20, 2022
- February 20, 2023

* - :doc:`1.10.5 LTS </release/1.10.5>`
- January 14, 2020
- February 20, 2022
- February 20, 2023

* - :ref:`1.10.4 LTS <whats_new_1104>`
- September 26, 2019
- February 20, 2022
- February 20, 2023

* - :ref:`1.10.3 LTS <whats_new_1103>`
- April 1, 2019
- February 20, 2022
- February 20, 2023

* - :ref:`1.10.2 LTS <whats_new_1102>`
- October 13, 2018
- February 20, 2022
- February 20, 2023
- December 31, 2025
13 changes: 2 additions & 11 deletions doc/release/eol_versions.rst → doc/release/eos_versions.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,23 +1,14 @@

EOL versions
EOS versions
============

This page lists release notes for Tarantool versions that have reached
their end of life in accordance with the :doc:`release policy <policy>`.
their end of support in accordance with the :doc:`release policy <policy>`.
See the :doc:`release calendar <calendar>` for more information.

.. toctree::
:maxdepth: 1

2.10.8
2.10.7
2.10.6
2.10.5
2.10.4
2.10.3
2.10.2
2.10.1
2.10.0
2.8.4
2.8.3
2.8.2
Expand Down
25 changes: 22 additions & 3 deletions doc/release/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -6,9 +6,11 @@
Releases
========

This section contains release notes for Tarantool versions from 1.6 to 2.11.
This section contains links to release notes for Tarantool versions 2.10 and 2.11.

For information about earlier release series, see :doc:`EOS Versions <eos_versions>`.
For information about newer release series, see the corresponding version's
documentation.
`documentation <https://www.tarantool.io/en/doc/latest/release/>`_.

To download Tarantool releases, check the `Download <https://www.tarantool.io/en/download/>`_ page.

Expand All @@ -27,8 +29,25 @@ To learn more, read the :doc:`Compatibility guarantees <compatibility>` article.
.. toctree::
:maxdepth: 1

2.11.8
2.11.7
2.11.6
2.11.5
2.11.4
2.11.3
2.11.2
2.11.1
2.11.0
eol_versions
2.10.8
2.10.7
2.10.6
2.10.5
2.10.4
2.10.3
2.10.2
2.10.1
2.10.0
eos_versions

.. toctree::
:maxdepth: 2
Expand Down
24 changes: 13 additions & 11 deletions doc/release/legacy-policy.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,11 +1,13 @@
Tarantool legacy release policy
===============================

This release policy is actual for Tarantool releases from ``1.6`` and until ``2.8.4`` inclusive.
Starting from the ``2.10.0`` release, a more actual :doc:`release policy <policy>` is applied.

A Tarantool release is identified by three digits, for example, 2.6.2 or 1.10.9:
A Tarantool release is identified by three digits, for example, ``2.6.2`` or ``1.10.9``:

* The first digit stands for a MAJOR release series that introduces
some *major changes*. Up to now, there has been only one major release jump
some *major changes*. One of major release jumps, for example, has happened
when we delivered the 2.x release series with the SQL support.
* The second digit stands for a MINOR release series that is used for
introducing new *features*.
Expand All @@ -22,14 +24,14 @@ So, each MINOR release series goes through a development-maturity life cycle
as follows:

1. **Alpha**. Once a quarter, we start off with a new alpha version,
such as 2.3.0, 2.4.0, and so on. This is not what an alpha release usually
such as ``2.3.0``, ``2.4.0``, and so on. This is not what an alpha release usually
means in the typical software release life cycle but rather the current trunk
version which is under heavy development and can be unstable.
The current alpha version always lives in the master branch.

2. **Beta**. When all the features planned are implemented, we fork a new branch
from the master branch and tag it as a new beta version.
It contains ``1`` for the PATCH digit, e.g., 2.3.1, 2.4.1, and so on.
It contains ``1`` for the PATCH digit, e.g., ``2.3.1``, ``2.4.1``, and so on.
This version cannot be called stable yet (feature freeze has just been done)
although there are no known critical regressions in it since
the last stable release.
Expand All @@ -38,11 +40,11 @@ as follows:
Finally, after we see our beta version runs successfully in
a production or development environment during another quarter while we fix
incoming bugs, we declare this version stable. It is tagged with ``2`` for
the PATCH digit, e.g., 2.3.2, 2.4.2, and so on.
the PATCH digit, e.g., ``2.3.2``, ``2.4.2``, and so on.

We support such version for 3 months while making another stable release
by fixing all bugs found. We release it in a quarter. This last tag
contains ``3`` for the PATCH digit, e.g., 2.3.3, 2.4.3, and so on.
contains ``3`` for the PATCH digit, e.g., ``2.3.3``, ``2.4.3``, and so on.
After the tag is set, no new changes are allowed to the release branch,
and it is declared deprecated and superseded by a newer MINOR version.

Expand All @@ -54,7 +56,7 @@ release series:

* **LTS (Long Term Support)** is a release series that is supported
for 3 years (community) and up to 5 years (paying customers).
Current LTS release series is 1.10, and it receives only PATCH level
Current LTS release series is ``2.11``, and it receives only PATCH level
releases.

* **Standard** is a release series that is supported only for a few months
Expand Down Expand Up @@ -92,14 +94,14 @@ by an example of some latest releases and release series:
*Support* means that we continue fixing bugs. We add bug fixes simultaneously
into the following release series: LTS, last stable, beta, and alpha.
If we look at the release diagram above, it means that the bug fixes are to be
added into 1.10, 2.4, 2.5, and 2.6 release series.
added into ``1.10``, ``2.4``, ``2.5``, and ``2.6`` release series.

To sum it up, once a quarter we release (see the release diagram above for
reference):

* next LTS release, e.g., 1.10.9
* two stable releases, e.g., 2.5.3 and 2.6.2
* beta version of the next release series, e.g., 2.7.1.
* next LTS release, e.g., ``1.10.9``
Copy link

@sergos sergos Nov 12, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Formally, only if there are fixes available by the release time.

Copy link
Contributor Author

@AArdeev AArdeev Nov 13, 2025 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Meaning 2 other releases are not guaranteed?

* two stable releases, e.g., ``2.5.3`` and ``2.6.2``
* beta version of the next release series, e.g., ``2.7.1.``

In all supported releases, when we find and fix an outstanding CVE/vulnerability,
we deliver a patch for that but do not tag a new PATCH level version.
Expand Down
Loading