Comment on Jellyfin 10.11 RC1 Released

• timbuck2themoon@sh.itjust.works ⁨3⁩ ⁨days⁩ ago

  I’ll be honest, Im not sure why theyre not releasing this as 11.x.

  This seems to be a major update. From what I can tell there are API changes, plugins might not work, your entire db is converted to another format, etc.

  I’m excited for it and thankful for all the work- just seems so big that it should be tagged 11.0.0

  source

  • stevestevesteve@lemmy.world ⁨3⁩ ⁨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 ⁨3⁩ ⁨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 ⁨3⁩ ⁨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

        • -> View More Comments
    • ShortN0te@lemmy.ml ⁨3⁩ ⁨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 ⁨2⁩ ⁨days⁩ 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

        • -> View More Comments
• victorz@lemmy.world ⁨3⁩ ⁨days⁩ ago

  any DB access now goes through the core library

  Out of curiosity, this is better because of encapsulation? Protection from bad plugins?

  source

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

    Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.

    source

    • victorz@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Brilliant. 👍

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

    Also for internal use. The original emby source used not within the code base standardized database access.

    Basically changes to the database were not possible since finding references across the code base which part uses which values was impossible.

    source

    • victorz@lemmy.world ⁨3⁩ ⁨days⁩ ago

      Ew. Yeah, good changes coming in that case. Glad they ironed that out!

      source