SentaiBrad said
With these quick updates we're kind of taking the Philosophy from Kodi. Any release that ends in .0 is a feature release with some bug fixes, a .1, .2 or .3 release are bug fix releases almost entirely. It's kind of comforting that, even with Kodi as big as they are, no matter how many Beta's or RC's they do most bugs still get found after the official release, so in that sense are kind of adopting it so that these releases make it to everyone. It's surprising and understandable why most users don't update to Beta's.
Also Cid! LOL I love that image.
Yea Derek, a good bad thing. xD
You should use semantic versioning, it's pretty standard and gives the user some context about how much has changed in the new version:
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compatible manner, and
PATCH version when you make backwards-compatible bug fixes.
Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.
http://semver.org/
The current version would be 6.0.2 in this scheme