Comment on Jellyfin 10.11 RC1 Released

• stevestevesteve@lemmy.world ⁨2⁩ ⁨days⁩ ago

  I kinda agree here. jellyfin.org/docs/general/…/release-procedure/

  Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.

  source

  • exu@feditown.com ⁨2⁩ ⁨days⁩ ago

    Their reasoning is literally the second sentence on that page.

    Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases if required for later cleanup work

    Any 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.

    source

    • evulhotdog@sh.itjust.works ⁨2⁩ ⁨days⁩ ago

      Sure they put a not in, but why not just follow semver to begin with instead of using semver with a bunch of asterisks, and essentially ignoring what semver is

      source

      • ShortN0te@lemmy.ml ⁨1⁩ ⁨day⁩ ago

        Consider the 10.y.z simply to be 0.y.z and everything works out.

        Jellyfin inherited a lot of shitty code and architecture from emby. They simply cannot guarantee anything across patches until it is sorted out.

        imho much better then releasing major version after major version because the break stuff regularly.

        source
  • ShortN0te@lemmy.ml ⁨2⁩ ⁨days⁩ ago

    Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

    Its right there at the link you posted.

    source

    • stevestevesteve@lemmy.world ⁨1⁩ ⁨day⁩ ago

      “Breaks all compatibility [with emby]” was my interpretation of that. Not a huge deal either way but I’d definitely have been calling it 11 with this DB rework myself

      source

      • ShortN0te@lemmy.ml ⁨1⁩ ⁨day⁩ ago

        … and may also break compatibility with previous 10.Y releases if required for later cleanup work.

        If you read through the whole paragraph, it is clear that they mean the compatibility of previous jellyfin versions.

        Also, again:

        Note however that the 10.Y.Z release chain represents the “cleanup” of the codebase, so it should be accepted that 10.Y.Z breaks all compatibility,

        That means that the code is not cleaned up with that release.

        If you would release 11 before the code is considered cleaned up, you would basically break your own defined versioning convention. That is best decided by the active maintainers.

        source