- cross-posted to:
- opensource@programming.dev
- opensource@lemmy.ml
- jellyfin@lemmy.ml
- cross-posted to:
- opensource@programming.dev
- opensource@lemmy.ml
- jellyfin@lemmy.ml
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.
You must log in or register to comment.
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
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.New funcionality I would like to see would be SSO with OIDC without an exterrnal plugin 😁
Maybe then we get v11
Same dude… Same
In traditional versioning systems you only jump major versions if you break compatibility with previous versions. For instance Semantic Versioning.
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.
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.
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
Unless the media also uses HDR in which case the server will still be required to transcode.
The startup UI is a neat idea
