[5pt] Clarify difference in features per tarantool version

[Totktonada]

Clarify difference in features per tarantool version

Product: Tarantool.
Since: 2.1.
Audience/target: customer / developer.
Root document: <new page>.
SME: @kyukhin.
Peer reviewer: @ documentarian name

Details

The idea is to create a table with notable features per tarantool version. Example (I just reformatted notable changes from 2.8.1 release notes with appropriate rephrasing):

Since version	Feature
2.8	Multiple iproto threads (gh-5645)
2.8	Set box.cfg options with environment variables (gh-5602)
2.8	box.ctl.promote() and the concept of manual elections (gh-3055)
2.8	Friendly LuaJIT memory profiler report (gh-5811)
2.8	--leak-only LuaJIT memory profiler option (gh-5812)

I would consider 1.10 as the baseline and would start to describe features since 2.1. I would start from 2.8, than 2.7, etc down to 2.1.

Please, collect notable changes from release notes first. Then ask the server team (especially, teamleads) for feedback. We can iterate this process per version: for 2.8, 2.7, etcd to eat the pie step by step.

Definition of done

• 2.8
  • Notable changes are collected from release notes.
  • Server teamleads confirmed that there were nothing more worthful to add in given version.
• 2.7
  • Notable changes.
  • Server team feedback.
• 2.6
  • Notable changes.
  • Server team feedback.
• 2.5
  • Notable changes.
  • Server team feedback.
• 2.4
  • Notable changes.
  • Server team feedback.
• 2.3
  • Notable changes.
  • Server team feedback.
• 2.2
  • Notable changes.
  • Server team feedback.
• 2.1
  • Notable changes.
  • Server team feedback.
• 2.1—2.8
  • Delivery teamleads confirmed that now it is easy to explain to our customers the perks of the new versions
  • Presale team feedback
  • Products feedback.

Planning checklist

• Pick product label:
  • server for Tarantool core
  • cartridge,
  • tdg, or
  • ecosystem
    for tools and connectors.
• Pick type label:
  • reference,
  • getting started,
  • user_guide, etc.
• Estimate complexity in storypoints in the title
• Add to Documentation board → Backlog