3301
First screenshot of Sync for Lemmy (lemmy.world)
submitted 3 years ago* by 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
[โ€“] 19 points 3 years ago (7 children)

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

  • permalink
  • fedilink
  • source
  • hideshow 7 child comments
    •
  • [โ€“] 23 points 3 years 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [โ€“] 31 points 3 years 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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [โ€“] 8 points 3 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [โ€“] 11 points 3 years 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 ยฏโ \โ _โ (โ ใƒ„โ )โ _โ /โ ยฏ

  • permalink
  • fedilink
  • source
  • parent
  • [โ€“] 3 points 3 years ago (1 child)

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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •