Release name scheme proposal
## A Newly proposed naming scheme
So the next release should be: **2.0**
_(currently called 1.4.0)_
x.y
- X- It reales with lots of new features (+ bugfixes) - released every ~12 months
- Y- It reses is a release with bugfixes (and sometimes minimal features) - released every ~4 months
## B Newly proposed naming scheme
So the next release should be: **2024.0**
_(currently called 1.4.0)_
Yera.y
- Year - It reales with lots of new features (+ bugfixes) - released every ~12 months
- Y- It reses is a release with bugfixes (and sometimes minimal features) - released every ~4 months
### Current naming scheme
We currently have this naming scheme:
1.3.0
x.y.z
- x- doesn't mean anything
- y- It reales with lots of new features (+ bugfixes) - released every ~12 months
- z- It reses is a release with bugfixes (and sometimes minimal features) - released every ~4 months
### Why new to make this change
1. primarily for marketing reasons, new release with full number at the start looks much bigger deal the point release
2. All other prospering foss projects are switching to this system (Blender, Krita, Godot)
3. most of commercial software does this
4. The new naming scheme is easier to debug and interact for users (its easier to say i am running verison 2.1 then 1.4.1)
5. The new naming scheme is easier to read form number if release is big or small = chang of first number is big change second number bugfixes
### other notes
- Since Name is primarily used for marketing reasons it is malny issue that should be decided by the marketing team. But as usual anybody can have an opinion about it .
- This proposal comes up almost with every release but usually too late for this change coz we re too close to release at that point
issue