versioning example.

So how does it work?
Versioning starts at ​​0.0 and should be at 0.1 once it’s usable and ready for the public.

Major releases
Every time you release a new major update, you increment the second number in the version by one. So for example : 0.1 turns into 0.2, 0.2 turns into 0.3 and so on…

The first number in the version is unused and is there purely for looks. Do not change it, as it will not look good.

Minor releases
Have you written a couple of new functions or fixed one or two bugs here and there and decided to release a minor release? Well that’s just great!

There are two ways to mark minor versions.

The first way is to add a hyphen, followed by the character “R” and the minor release number. (Minor release numbers start from 1)
For example, let’s say the current version is 0.1. If you were to release your first minor release it would become 0.1-R1. Pretty straight-forward, right!?

The second way is to add a letter at the end of the version if it’s not present already, and increment it if it is. So 0.1 with a patch becomes 0.1a. 0.1a with another patch becomes 0.1b.
However, the English alphabet only contains 26 letters. What do I do once I reach “z”?
Well, that’s pretty simple. Append another new letter to the end. Thus, 0.1zwill become 0.1za and so on…

Lets say you had issues learning the alphabet back in primary school, you can simply skip almost the entire alphabet and go from “d” to “x”. This is also perfectly valid.

Now, which one should I choose?
The answer is very simple, choose whatever you want. And feel free to switch between the two whenever you want, this won’t cause any confusion what so ever. If you feel like it, you can even use both at the same time (0.3zb-R28). All of this is perfectly valid. Personally, I prefer using both. As that way you can make sure that people who don’t know the alphabet will know what the current minor release is and vice versa.