2.11 calendar and release information update #5340
Conversation
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
There was a problem hiding this comment.
We need to update the picture: latest release is 2.11.8
There was a problem hiding this comment.
Can you please share EOL /EOS dates for 2.11.8?
doc/release/calendar.rst
Outdated
|
|
||
| .. note:: | ||
|
|
||
| *End of life* (*EOL*) means the release series will no longer receive any patches, |
There was a problem hiding this comment.
no longer receive
I'd like to add something like "regular" or "automatic" - means we won't backport all fixes for the problems found, still some releases can appear beyond this point. Example: critical fixes, vulnerability, etc.
doc/release/index.rst
Outdated
| ======== | ||
|
|
||
| This section contains release notes for Tarantool versions from 1.6 to 2.11. | ||
| This section contains links to release notes for Tarantool versions from 2.10.0 to 2.11. |
There was a problem hiding this comment.
from 2.10.0 to 2.11.
Perhaps just "2.10 an 2.11"?
doc/release/legacy-policy.rst
Outdated
| * **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 ``1.10``, and it receives only PATCH level |
There was a problem hiding this comment.
No. Current LTS is 2.11. The 1.10 series is EOL and EOS - no more patches expected.
| * 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`` |
There was a problem hiding this comment.
Formally, only if there are fixes available by the release time.
There was a problem hiding this comment.
Meaning 2 other releases are not guaranteed?
doc/release/policy.rst
Outdated
| end of life (EOL) stage. | ||
| No new versions are released since then. | ||
| Eventually, the release series reaches the end of life (EOL) date and stops | ||
| receiving any patches, updates, or feature improvements. Some time after that, |
|
|
||
| See all currently supported Tarantool versions visualised as :doc:`a calendar <calendar>` | ||
| or as :ref:`a release lifetime table <release-table>`. | ||
| See all currently supported Tarantool 2.x versions visualised as :doc:`a calendar <calendar>` |
There was a problem hiding this comment.
Perhaps we have to switch to 3.x series as a current one in development. 2.x has only one LTS version which is already reached it EOL milestone.
There was a problem hiding this comment.
The initial idea was to separate 2.x from Latest. The link to the Latest documentation is provided on the 2.x Calendar page. Although if it feels critical i can add it here, too
| see the corresponding `page <https://www.tarantool.io/en/doc/latest/release/>`_. | ||
|
|
||
| .. container:: table | ||
|
|
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Great suggestion, where to get actual dates from? (i put a "not planned yet" EOL/EOS for 2.11.8 for now)
There was a problem hiding this comment.
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?
sergepetrenko
left a comment
sergepetrenko
left a comment
There was a problem hiding this comment.
Thanks for the patch!
github-actions
bot
temporarily deployed
to
branch-gh-5282-2-11-calendar-and-release-info
Fixes #5282