Guide to contributing, release versioning
When you are a maintainer or even admin, you shouldn't just randomly click-post a version like that. You will have to follow some specific requirements on versioning.
As I said, you don't just post the release right away following the numerical order of the decimals. What I mean is using something like:
0.0.1 -> 0.0.2 -> 0.0.3 -> 0.0.4 -> 0.0.5 -> 0.0.6 -> 0.0.7 -> 0.0.8 -> 0.0.9 -> 0.1.0
When you do that style, it's kinda confusing to look but it's more common sense. Haven't you noticed some popular software versions reaching something like v1.90.15? They actually use a software versioning rule called Semantic Versioning. Some software uses the date or labels like -alpha though.
To use this method, you change some specific digits on the release.
Note: You only use 3 digits for the version.
If you made patches or just fixed a bug, you update the very last digit of the version.
Ex.: 0.0.1 turns into 0.0.2 after fixing a bug
On the other hand, when you made a new feature, update the middle digit of the version.
For example, the version 0.0.1 turns into 0.1.0 because of the feature
Note: When you add a new feature, you update the middle digit right? You actually also make the last digit a whole 0
For major changes that break the current programs that is based on the previous version.
Don't understand? Let's say that a script is using the old current keyword to output something (out), but you changed it to say so the script doesn't work anymore.
Then you change the very first digit and change all of the other digits into 0
I chose to use this kind of versioning since the change could be recognized instantly. If you look at the version v0.1.0 and the program is using that "common-sense" method, you'll have to browse the releases and look for a description to see what changed. In this method, instead of looking at the releases page, you instantly know what changed.
We use the stable release, as we can have more time adding stuff and less risk of having bad code. So please use the point release please.
Author of this page: Johnryzon Z. Abejero (johnryzon123)