Clarify release process: version numbering and changelogs

[gggeek]

First of all, thanks for maintaining this piece of software.

Then, if I may ask, would it be possible to clarify a bit, and maybe improve, the process used in new releases?

• the version numbers seem to be bumped up in an irregular fashion, at least as far as the releases available on Github are concerned. ex: 1.9.9 is followed by 2.2.12 ?
• also, there does not seem to be in git any tag mentioning the revisions in between 1.9.9 and 2.2.12
• last but not least, there seem to be no release notes / changelog for most releases. Personally, I am a fan of manually curated changelogs, but at least a list of bugs fixed would do (which is generally better than a list of all commits)

[jmrenouard]

Hi @gggeek ,

Last release is here
https://github.com/major/MySQLTuner-perl/releases/tag/v2.5.2

Sorry, for this annoying situation :D

This script is a semi professional/hobby activity

As soon as I'm fixing issue and add extra minor changes, I will stay on 2.5.x version

2.6.x will be release for bigger features like decent replication analysis, template for report, ...

3.0.x should be a big game change: like web service connection or complete rewrite in an other language

Are you OK with this versioning approach ?

P.S: This ugly situation came for my test on auto increment script(Makefile) for release version, I think this issue also help me to clarify my own mind

Best regards,
@jmrenouard