(discussion) change WLED versioning scheme to Major.minor (.patch-label)

[softhack007]

Please allow me to re-open an old discussion.

Past WLED releases have followed a 0.major.minor_or_patch-info scheme, which seems to originate from a pattern that was popular on github about 14 years ago. My proposal (discussion welcome) is to simply drop the leading 0. .

Why: the main reason is that 0. does not have any real meaning any more, and most users are deliberately omitting this prefix any way.

For example, the next WLED release could be 16.0 (instead of 0.16.0), and we would be able to follow the numbering scheme recommended by semver.org

• MAJOR version when you make incompatible API changes, or new features are not fully backwards compatible
• MINOR version when you add functionality in a backward compatible manner
• PATCH version when you make backward compatible bug fixes
• Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

What do you think?

[DedeHai]

I am fine with this in general. It may affect third-party code if the current pattern is somehow hard-coded, just about the only thing I can think of that could complicate things.