[SM-Commit] GIT changes to master grimoire by Thomas Orgis (e70bf15c04d5b765a31e0b254701de242d3c352c)
thomas-forum at orgis.org
Sat Feb 3 20:06:58 EST 2007
Am Sat, 3 Feb 2007 18:48:49 -0600
schrieb Jeremy Blosser <jblosser-smgl at firinn.org>:
> > + this is version 2.2.2 for keeping consistency
> I'm not one who really cares about version numbers but you just bumped it
> to 2.2.1 and only really changed 1 line between now and then.
I hesitated myself, but I made one minor fix and increased the minor minor version number... 2.2.1
Then the next fix occured and well... since I already had the other one pushed, it was out there.
Most probably not in the tarball that quickly, but anyway.
I think it is better to make apparently proactive version number changes than to slip "just another small fix" into an already released version.
That practice gives us bad checksums when upstream sources do small changes and keep version number constant.
I agree that in practice there wouldn't be anyone noticing the timeframe between the first 2.2.1 and the second 2.2.1, but faced even with the theoretical possibility and as a matter of principle, I just incremented that number.
Something small happened and that is what an increase of 0.0.1 says.
More information about the SM-Commit