Follow-up сalendar and release information update
Open
@AArdeev is already working on this.
Since Jul 23, 2025.
2.11
3.0
- Dominant language
- CSS
- Stars
- 15
- Forks
- 49
- Avg merge
- 1d 13h
- Merged PRs (30d)
- 3
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 https://github.com/tarantool/doc/issues/5281; https://github.com/tarantool/doc/issues/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.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.