Jellyfin 10.11.0 RC9

https://github.com/jellyfin/jellyfin/releases/tag/v10.11.0-rc9

Jellyfin, the open source media server, has released their 9th RC for version 10.11.0.

This is a preview release, intended for those interested in testing 10.11.0 before it’s final public release.

If you intend to test this, BE SURE you stop your Jellyfin server and take a full backup before upgrading!

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

See the GitHub link for more details and a full list of changes.

157 points · 10 comments · view on lemmy.world

10 Comments

morethanevil@lemmy.fedifriends.social · 17 pts · 323d (6 replies)

Can not wait for final release, but why v10.11? Such big changes.. V11 would be better imo 🤔

Anyway thanks to the devs for this great release

Mountaineer@aussie.zone · 16 pts · 323d (2 replies)

I think the feel from the Devs is that there isn't enough new functionality to justify the major version bump, this primarily being a reimplementation of existing features.

BUT, I agree with you, it should definitely be V11 under the semantic versioning scheme.
Whilst there is a migration path here, the database changes under the hood alone are likely to break backwards compatibility with all plugins (with in-house plugins being upgraded in sync).
Such breakage is kind of the defining characteristic of a MAJOR version.

morethanevil@lemmy.fedifriends.social · 18 pts · 323d (1 reply)

New funcionality I would like to see would be SSO with OIDC without an exterrnal plugin 😁

Maybe then we get v11

bitwolf@sh.itjust.works · 4 pts · 322d

Same dude.... Same

atomicbocks@sh.itjust.works · 7 pts · 323d (2 replies)

In traditional versioning systems you only jump major versions if you break compatibility with previous versions. For instance Semantic Versioning.

Strit@lemmy.linuxuserspace.show · 8 pts · 323d (1 reply)

Which they do here. Once you upgrade to 10.11, your database is not 10.10 compatible anymore. So you can't downgrade without restoring a backup.

atomicbocks@sh.itjust.works · 2 pts · 322d

If an app will work with both without needing to change its API then that counts even if it can’t use the new features.

mlg@lemmy.world · 12 pts · 323d (1 reply)

HEVC support is enabled for Firefox 134

Cool for anyone not using AV1 which I assume is a big chunk of the userbase because not everyone has good AV1 hardware acceleration lol

Chewy7324@discuss.tchncs.de · 3 pts · 321d

Unless the media also uses HDR in which case the server will still be required to transcode.

southernbeaver@lemmy.world · 11 pts · 323d

The startup UI is a neat idea