Can you suggest a reasonable way to increment script version? E.g. how many bugs fixed without changing db then increment release version, how many bugs fixed with db change then increase minor version… Any suggestions?
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.
I don’t think there is any standard as to how many bugs get fixed per version release.
I think it depends on how many bugs you want to still be out there while you’re fixing things.
Probably the only time you should “rush” a version release is for critical updates, other than that some sort of convenient regularly timed schedule should be fine.
I know that I meant when I release a patch how much should I increment the release version? only +1 for each release? (e.g. 1.0.0 to 1.0.1) or it depends on how many bugs are fixed, that I increment +2 at once, e.g. 1.0.0 to 1.0.2 directly? If more than +1 then how should I incrmenet it for how many bug fixes?
Oh, I see. I think only +1 is fine. In my experience, it’s only ever been for marketing reasons when you would do more than that.
Some versioning schemes use an odd-even sequence eg. odd# signifies development and even# signifies stable.
But I think +1 is more widely used and better known and understood.