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.
You must log in or register to comment.
i gave emby and jellyfin a testrun yesterday using docker. I kept emby because i can easily add smb shares using the webinterface. jellyfin requires me to mount those to the host/container. am i using jellyfin wrong?
Is there a buried lede here? What’s noteworthy about an RC of a minor version release?
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.
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
I kinda agree here. https://jellyfin.org/docs/general/contributing/release-procedure/
Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.
Their reasoning is literally the second sentence on that page.
Note however that the
10.Y.Zrelease chain represents the “cleanup” of the codebase, so it should be accepted that10.Y.Zbreaks all compatibility, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous10.Yreleases if required for later cleanup workAny 10.Y.Z release is cleanup and can include breaking changes. That’s been the case for 10.9 and 10.10 already btw.
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.
any DB access now goes through the core library
Out of curiosity, this is better because of encapsulation? Protection from bad plugins?
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.
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.
I’m serious, there’s so much lazy posting on Lemmy regarding software releases.
- no mention of what the software is or does ✔️
- no mention of what’s interesting about the software or this release. ✔️
Jellyfin is quite a big name, but still, the pattern is clear.
We could have a tag for things like this (if tags are a thing on lemmy) or a required prefix, such as "Software release: ".
I do like to see an announcement for things I use and have slow release schedule.
Sorry, I didn’t realize some Lemmy clients don’t show cross-post descriptions. I’ll copy paste it below:
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.
