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

Sync for Lemmy

15137 readers
13 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: @MargotRobbie@lemmy.world


founded 1 year ago
MODERATORS
 

@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 (7 children)

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

[โ€“] Orvanis@lemm.ee 23 points 1 year ago (6 children)

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 (4 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

[โ€“] schnex@reddthat.com 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

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

load more comments (2 replies)
load more comments (3 replies)
load more comments (3 replies)