Consider versioning gitlab as YY.M in the future (possibly after version 13)

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Close this issue

Proposal

Today we need to write future releases like this 14.0 (2021-05-22) because it is not clear from the version itself what date it will come out, the further ahead the release is from today the more difficult it becomes to calculate the correct target release date for a feature.

It might be a good idea to instead of using v14 jump straight to 21.5.0.

Gitlab 21.5 (is May 2021).. Gitlab 24.6 (is Jun 2024).. Gitlab 54.3 (is Mar 2054)

The primary technical advantage would be reducing the cognitive load in reading Milestones when managing issues, translating them to dates becomes more natural and straightforward.