Version numbering suggestions

[Valnjes]

Its very confusing to have the same version number for a complete two different version.

Let me suggest you the new numbering system that would make sense and give info on a glance.

AA.BB.CC

AA -> current branch, as for now its in the "beta" phase, it will remain 0 (00) for now
BB -> stable or test build, if the number is even, then its stable, like 36, if its uneven, then it is a test build, like 35 or 37
CC -> build number of the branch, so 01 for the build 1, 12 for the build 12 etc

As for now the last two releases have this number:
0.37.0 -> two of them with the same name, but different time of releases and size:

So, as we have two 0.37 build, let one be 0.37.0 and the other be 0.37.1.
When the test build are stable, push them to release as 0.38.0, and if the stable release needs a hotfix, then it will be 0.38.1 and so on.
And the test builds will then be 0.39.0 etc.

Does this make sense to you? On a glance everyone will know what branch and release they are using, and the numbering would be fixed.

[MoazSalem]

Its very confusing to have the same version number for a complete two different version.

Let me suggest you the new numbering system that would make sense and give info on a glance.

AA.BB.CC

AA -> current branch, as for now its in the "beta" phase, it will remain 0 (00) for now BB -> stable or test build, if the number is even, then its stable, like 36, if its uneven, then it is a test build, like 35 or 37 CC -> build number of the branch, so 01 for the build 1, 12 for the build 12 etc

As for now the last two releases have this number: 0.37.0 -> two of them with the same name, but different time of releases and size:

So, as we have two 0.37 build, let one be 0.37.0 and the other be 0.37.1. When the test build are stable, push them to release as 0.38.0, and if the stable release needs a hotfix, then it will be 0.38.1 and so on. And the test builds will then be 0.39.0 etc.

Does this make sense to you? On a glance everyone will know what branch and release they are using, and the numbering would be fixed.

If you track my versioning in the issues, you will be lost.

I know it's confusing, but this is not how versioning works. AA would be a major change that could have breaking changes. BB is mostly minor changes aka small features added, CC is bug fixes and patches.

most of the time i am working on multiple things at the same time, so i skip changing most of the time, also changing the version is manual, and i just skip it while testing changes because i don't know if what i did actually fixed it or not, you will see me mostly changing the version after closing an issue not during it, i am considering doing beta or nightly releases sometime soon instead of full releases only, it would have me do better versions numbering at least, instead of currently i think the next version is 0.40.0 since i did a lot of changes but didn't pump the number correctly.