[FEATURE] Versioning system is going too fast.

[anf]

Is your feature request related to a problem? Please describe.
At this moment, BotANF is 15% closer, by versioning to v3.0. Which shouldn't be like that because BotANF is barely even set up.

Describe the solution you'd like
Move back the versioning to an appropriate number. Something like 2.01.x.

Describe alternatives you've considered
A new versioning system with 4 component format; Assembly Versioning. It goes like: X.X.X.X.
This is the char that I've designed for it:

Number	Description
Redesign	Rewrite of the bot, only changed by the server owner(s)
Feature	Additions in components of the bot that are neither minor nor major
Minor	Small changes added or updated, typo fixes
Patch	Bug fix

Additional context
Versioning system needs to be fixed and implemented correctly.

[yiliansource]

May I suggest using semantic versioning (or semver for short) instead of assembly versioning?

Semantic versioning is designed specifically for the purpose of having a structure throughout the versioning of a project, while the assembly version is just used by the CLR to determine which version of the assembly to load.

The assembly version is what the CLR uses at run time to select which version of an assembly to load.

This is also useful if you have a project that either spans multiple assemblies, or additional resources that are not included in it, because then the assembly version will no longer be of (proper) use.

[tomlin7]

upvote