Open
Description
Product: Tarantool
Since: 2.11, 3.x
Root document: https://www.tarantool.io/en/doc/latest/release/ ; https://www.tarantool.io/en/doc/2.11/release/
SME: @ hackallcode
Details
Follow up to #5167
Priority tasks:
- Pages https://www.tarantool.io/en/doc/latest/release/ ; https://www.tarantool.io/en/doc/2.11/release/calendar/.
Separate calendar (keep 3.x in "latest", move 2.x to "2.11"). Limit calendar in "2.11" with 2026. Add references from "latest" to "2.11" and vice versa. - Table https://www.tarantool.io/en/doc/latest/release/#supported-versions.
Separate data (keep 3.x in "latest", move 1.x & 2.x to "2.11"). - Page https://www.tarantool.io/en/doc/latest/release/eol_versions/.
Remove anything older than 3.0.0 from the table and delete the note before the table. - Left menu of https://www.tarantool.io/en/doc/latest/release/eol_versions/.
Move everything but Tarantool 3.0 & Tarantool 3.1 to "2.11". - The "latest" contains Tarantool 3.0 and Tarantool 3.1 releases in 2 sections at the same time: "Releases" and "EOL Versions". Both releases must be either presented only in the "EOL versions" section or the very "EOL Versions" section must be removed. In the latter case, the EOL info should be either marked next to the version's name (Tarantool 3.0 EOL), or provided as an information (warning, note) box inside of the page.
Next follow up ideas (to be discussed)
- Think of a new structure for the Left menu and versions representation in the Releases submenu. Maybe there is a sense in renaming the submenu in Release Info and grouping releases 3.0-3.4 to the Releases group.
- In "2.11", all releases are EOL, therefore the EOL Versions section seems excessive.
- There are 2 tables that contain very similar information (
/release/and/release/eol_versions/). Consider joining data from both tables in just one table. Patch dates are preferable to keep as well. - Pages of releases - release dates to be removed (substituted by EOL/EOS). The reason - only main release date is shown, and no dates for patches are there, which seems to be not really informative. On the other hand, if we show EOL/EOS dates on a release page, the reader might find it helpful in understanding timelines and planning future updates.