122
immich update has breaking changes (github.com)
submitted 2 years ago by to c/selfhosted@lemmy.world
39 comments fedilink hide all child comments
you are viewing a single comment's thread
view the rest of the comments
[–] 12 points 2 years ago (2 children)

There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver.

I am generally of the opinion that version numbers do not matter at all until the author/distributor has GUARANTEED that they do. Until then they're worthless, including in places where semver is supposedly enforced like NPM. If I had a penny for every NPM package that broke my project after removing the package-lock.json, I could retire.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 4 child comments
    •
  • [–] 4 points 2 years ago

    Absolutely agree with you. Just because the Versioning looks like x.y.z does not mean it follows that convention. The most prominent example is probably the Linux Kernel Versioning.

    Read the notes of the dev team and subscribe to the changelog or update channel.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 3 points 2 years ago

    There are quite a few mature projects in 0.x that would cause a LOT of pain if they actually applied semver

    Depending on how one defines the "initial development" phase, those projects are actually conforming to semver spec:

    Major version zero (0.y.z) is for initial development. Anything MAY change at any time. The public API SHOULD NOT be considered stable.

  • permalink
  • fedilink
  • source
  • parent