Untold1707Jun 9, 2025

Jellyfin 10.11 RC1 Released

https://lemmy.zip/post/40833824

Jellyfin 10.11 RC1 Released - Lemmy.zip

cross-posted from: https://lemmy.zip/post/40833329 [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 [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.

Show threaddgdftJun 9, 2025
Is there a buried lede here? What’s noteworthy about an RC of a minor version release?
Show threadexuJun 9, 2025
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.
Show threadtimbuck2themoonJun 9, 2025

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

Show threadstevestevesteveJun 9, 2025

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.

Releases | Jellyfin

This document is a guide for the core team, provided publicly to ensure transparency in the release process.

Show threadexu

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.

Jun 9, 2025 at 7:23pmWeb
Show threadevulhotdogJun 10, 2025
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
Show threadShortN0teJun 10, 2025

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.