• PieMePlenty@lemmy.world
    link
    fedilink
    arrow-up
    16
    ·
    4 months ago

    I recently realized: fuck it, just have the build date as the version: 2026.02.28.14 with the last number being the hour. I can immediately tell when something is on latest or not. You can get a little cheeky with the short year ‘26’ but that’s it. No reason to have some arbitrary numbers represent some strange philosophy behind them.

    • ilinamorato@lemmy.world
      link
      fedilink
      arrow-up
      13
      ·
      4 months ago

      Can you immediately tell? Do you memorize the last day you released? Do you release daily? There’s definitely some benefit to making the version equal to the date, but you lose all the other benefits of semver (categorizing the scope of the release being the big one). That’s not a strange philosophy, it’s just being a good api provider.

      • PieMePlenty@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        4 months ago

        You’re right. I’m looking at it through a very limited scope: nightly releases. I’ve been working with “latest” so long, I forgot actual versions exist.

    • gandalf_der_12te@discuss.tchncs.de
      link
      fedilink
      arrow-up
      1
      ·
      4 months ago

      I use 2026-03-01-05 too but the -05 does not represent the hour but the number of version i release today. like if i make five commits today, they will be -01, -02, -03, …

    • qarbone@lemmy.world
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      3
      ·
      4 months ago

      The philosophy is pretty straight-forward. I don’t know why the world is pretending it’s difficult.