Re: 1 cset was pushed to modules/sitecontact: oops - no upgrade wanted here ...forgot ...

I like the ability to add a suffix if i'm part way through doing a version. 
Jason showed me the trick and it's a quick way to instantly see that you 
have got the version installed with 'x' changes. For releases though I 
always stick to 3 part version numbers - it's enough ;)

Jo

"Marcel van der Boom" <[email protected]> wrote in message 
news:[email protected]...
> Jason Judge wrote:
>> So, the module upgrade process will *only* look at the first three parts
>> when comparing version numbers of a module.It will try to handle
>> non-standard version numbers sensibly, so 0.1.2 == 00.01.02 == .1.2. ==
>> 0.1.2.3.4.5.6 wrt upgrades.
>
> needlessly complicates stuff imo. its for me a matter of consistency. the 
> version number is there to trigger upgrades, even if that upgrade is a 
> noop. Having 3 numbers throughout makes everything easier, displaying, 
> calculating stuff, no need to check for exceptions if the version happens 
> to be longer etc.
>
> but, as always, its a devs choice. 10^3 combo's are apparently not enough 
> ;-)
>
> marcel