Skip to content

Follow-up сalendar and release information update #5219

@AArdeev

Description

@AArdeev

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 #5281; #5282

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.
  • 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.

Metadata

Metadata

Assignees

Labels

2.112.11 release and the associated technical debt3.0

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions