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.

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

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

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