I want to discuss with you our versioning strategy and possible change to new.
Currently our strategy is:
[details=Summary]Major - Major version is a definite release of the product. It increased when there are significant changes in functionality. I planed to show by this number that the project mature enough and cover all basic functionality.
Minor - Minor version is incremented when only new features or major bug fixes have been added.
Patch - Patch version starts with 0 and incremented only when bug has been resolved.
Build No - Build Number represent commits number past after last release.[/details]
This is good strategy, but according to my observations it doesn’t perfectly suit our purposes.
Major - Major version is a definite release of the product. It increased when there are significant changes in functionality.
According to our speed and number of changes at least versions 0.4.0 and future 0.5.0 could be major. These are significant releases for us. And because many users already use Valentina for making product ready patterns awaiting release 1.0 has less sense that it was at the beginning when i decided which versioning strategy to choose.
I don’t like stupid marketing, but as you maybe mentioned many users say v4 or v5, v4.5 instead of v0.4.5. Even i see that this is much more comfortable.
So, new strategy could be:
Description is almost the same as for the previous strategy. But each current minor release become major and minor number is not used anymore.
For example 0.5.0 will be 5.0.0. Next release with bug fixes will be 5.0.1, 5.0.2 and so on.
So, what do you think?