this post was submitted on 07 Jul 2023
3238 points (99.2% liked)

Sync for Lemmy

15088 readers
3 users here now

๐Ÿ‘€


Welcome to Sync for Lemmy!

Download Sync for Lemmy


Welcome to the official Sync for Lemmy community.

The rules for posting and commenting, besides the rules defined here for lemmy.world, are as follows:

Community Rules


1- No advertising or spam.

All types of advertising and spam are restricted in this community.



Community Credits

Artwork and community banner by: @[email protected]


founded 1 year ago
MODERATORS
 

@ljdawson shared on Discord

you are viewing a single comment's thread
view the rest of the comments
[โ€“] [email protected] 30 points 1 year ago (2 children)

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

[โ€“] [email protected] 8 points 1 year ago (1 children)

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

[โ€“] [email protected] 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 ยฏโ \โ _โ (โ ใƒ„โ )โ _โ /โ ยฏ

[โ€“] [email protected] 3 points 1 year ago (1 children)

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

[โ€“] [email protected] 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.