3288

First screenshot of Sync for Lemmy (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by eco@lemmy.world to c/syncforlemmy@lemmy.world

276 comments fedilink hide all child comments

@ljdawson shared on Discord

you are viewing a single comment's thread
view the rest of the comments

[-] drd@lemmy.ml 19 points 1 year ago

v23.07.08-00.34 already? This dev really gets to business.

[-] Orvanis@lemm.ee 23 points 1 year ago

In all seriousness, is the Dev using the build date as the version number....? July 8th, 2023 at 12:34am - vYY.MM.DD-HH.mm

Unusual approach for sure as you have no clue if it is a major version change or minor bug fixes.

[-] icesentry@lemmy.world 31 points 1 year ago

Using the date as a version number for an application that gets frequent updates is very standard. Most users will be expected to be on the latest version always.

There's even a website for it https://calver.org

[-] Orvanis@lemm.ee 8 points 1 year ago

Thank you for the web link, TIL it is much more common than I was aware!

[-] cypherix93@lemmy.world 11 points 1 year ago

Generally speaking, I find it easier and more intuitive to use. We use calver at work bc it seems pointless to identify if every week's release is major / minor / patch etc. My thought is the latest is the greatest - if something goes wrong, it'll be fixed in a later version ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

[-] schnex@reddthat.com 3 points 1 year ago

Interesting, I always found semantic versioning pretty useless, except for knowing that a new major release breaks existing APIs

[-] DoomBot5@lemmy.world 3 points 1 year ago

It's great to get a quick context of the size of the change expected. That does require the developer numbering the release to appropriately version it though.