Release 10.11.0 RC1 · jellyfin/jellyfin
github.com
🚀 Jellyfin Server 10.11.0 RC1 We are pleased to announce the first release candidate preview release of Jellyfin 10.11.0! This is a preview release, intended for those interested in testing 10.11.0...

cross-posted from: https://lemmy.zip/post/40833329

We are pleased to announce the first release candidate preview release of Jellyfin 10.11.0!

This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release. We welcome testers to help find as many bugs as we can before the final release.

As always, please ensure you stop your Jellyfin server and take a full backup before upgrading!

WIP release notes: https://notes.jellyfin.org/v10.11.0_features

This is the first release that uses the new EF Core database mapper. If you’d like to help test this release, please remember to remove all plugins to make debugging logs as easy as possible.

  • exu@feditown.comEnglish
    601·
    4 days ago

    This is the database rework that’s been in progress for a while to remove all the bad inherited database code from when the forked Emby. No more SQL statements in code or plugins, any DB access now goes through the core library. There are a few blog posts in their website with more details.

    • timbuck2themoon@sh.itjust.works
      English
      472·
      4 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

        • exu@feditown.comEnglish
          23·
          4 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.

          • evulhotdog@sh.itjust.worksEnglish
            143·
            3 days ago

            Sure they put a note 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?

            • ShortN0te@lemmy.mlEnglish
              61·
              3 days 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.

        • ShortN0te@lemmy.mlEnglish
          8·
          4 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.

          • stevestevesteve@lemmy.worldEnglish
            12·
            3 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

            • ShortN0te@lemmy.mlEnglish
              21·
              2 days 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.

    • Victor@lemmy.worldEnglish
      5·
      4 days ago

      any DB access now goes through the core library

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

      • stevestevesteve@lemmy.worldEnglish
        22·
        4 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.

      • ShortN0te@lemmy.mlEnglish
        9·
        4 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.