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.
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, …
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?
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.
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, …
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?