• mrgoosmoos@lemmy.ca
    link
    fedilink
    English
    arrow-up
    2
    ·
    9 hours ago

    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

      • mrgoosmoos@lemmy.ca
        link
        fedilink
        English
        arrow-up
        2
        ·
        3 hours ago

        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

    • username_1@programming.dev
      link
      fedilink
      arrow-up
      4
      ·
      9 hours ago

      1.21 to 1.211

      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!”

      • mrgoosmoos@lemmy.ca
        link
        fedilink
        English
        arrow-up
        1
        ·
        3 hours ago

        so I actually use various different systems depending on my mood that day.

        maybe I add a dash, maybe I use another decimal, maybe I use alpha characters.

        none of it matters because they’re wiped out a few hours later

    • grrgyle@slrpnk.net
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      8 hours ago

      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