that’s with the assumption that the smallest increment was used every time
I sometimes increment things by adding the next decimal place
note: I am not a developer, just a dude making tools at work. but I somehow always end up incrementing something now and then from 1.21 to 1.211 because I wanted to avoid the “1.21 new actually newest” situation and bumping to 1.22 didn’t make sense. it’s like temporary versioning for me, WIP files
So +190 increment is totally ok for you, but +1 sometimes “didn’t make sense”. IT DOESN"T MAKE ANY SENSE! Oh, and you can use letters. 1.21 -> 1.21a looks MUCH more explanatory for your purposes than “+1 is too harsh increase, so I’ll increase on 190!”
that’s with the assumption that the smallest increment was used every time
I sometimes increment things by adding the next decimal place
note: I am not a developer, just a dude making tools at work. but I somehow always end up incrementing something now and then from 1.21 to 1.211 because I wanted to avoid the “1.21 new actually newest” situation and bumping to 1.22 didn’t make sense. it’s like temporary versioning for me, WIP files
So +190 increment is totally ok for you, but +1 sometimes “didn’t make sense”. IT DOESN"T MAKE ANY SENSE! Oh, and you can use letters. 1.21 -> 1.21a looks MUCH more explanatory for your purposes than “+1 is too harsh increase, so I’ll increase on 190!”
Sub version tags make sense but for the the love of pie if you’re going to use a number at least separate it from the others, like
1.21-1= 0.21
;-)
Roffffl you’re pure evil
Bothers me that you wouldn’t go for 1.21.1 but you got the freedom to be WRONG. WRONG WRONG WRONG[1] if you want.
just teasing with this part of my reply :) ↩︎
I do that too sometimes lol but I’m just not a fan
if it were actual releases, yeah totally. but it’s just temporary files