Post #1665267

2026-02-28 09:43 UTC

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.

Replies (4)

@the_wonderfool@piefed.social 2026-02-28 10:35

Tried it in the past but ultimately abandoned it, as then release numbers lost all added meaning. I can remember what happened in release 2.0.0 or (kinda) 3.5.0, but what the hell was release 2025.02.15? Why did it break this random function?

Open ##1665361
@ilinamorato@lemmy.world 2026-02-28 10:12

*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.

Open ##1665362
@grrgyle@slrpnk.net 2026-02-28 13:41

I like using the short hash from the latest git commit used to build, to avoid confusion among multiple devs on parallel streams

Open ##1665363
@qarbone@lemmy.world 2026-02-28 13:01

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

Open ##1665371