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.
Media watch status no longer persists on media rename. When you move or rename your media files, previously Jellyfin remembered the watch status based on external IDs alone; now it uses an actual reference to the database entry. This is a transitional change and we are working on a better way to handle that in a future version.
I hope they do figure out a solution for that soon… Until that’s fixed I’m going to stay on 10.10.7 for a while.
Wow this one looks major, and possibly disruptive.
Dayum.
Some nice things in there!Important note: This release can only be upgraded to if you’re on 10.7 or later. Make sure to update to 10.10 soon or the process might become more manual.
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.
Sure they put a note 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?
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.
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.
“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
… 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.
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.
Brilliant. 👍
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.
Ew. Yeah, good changes coming in that case. Glad they ironed that out!
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.
I have to admit, it’s something I’d like to see done a bit better (not that I’d be the one posting about it typically)
“Crocoslut version 12 released!”
Uh… great?
Though sometimes you go to the website and it’s not much better.
Crocoslut really started going downhill after the license change and conversion to nodejs in v9.
Crocoslut is yesterday. AlligatorAlly is the more friendly fork!
Though sometimes you go to the website and it’s not much better.
Dude yes. Among my comments you’ll see that I ranted about this for a few days in the comments of another post. That’s even worse, when you can’t even find out for yourself.
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.
My client showed that to me and I read it. I just imagined myself as someone who doesn’t know what Jellyfin is, and that text didn’t help much.
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?
Why is it not mounted on the host/cointainer? I dont think you are using jellyfin “wrong” but its not like you cant just configure a mount point if you wanted to use jellyfin with it.
That is an interesting thing to point out though, im not actually sure but i think they used to support smb shares directly, i might just be thinking of kodi though.
it is not mounted to the container because that is a shit solution. the host would need to mount it and pass that to tge container. emby i stop the container and no connection to the share. mounted in host it would still be there. not to mention the hassle this also means more traffic. an idea why jellyfin doesnt do shares like emby?
Maybe because it’s not an obviously wanted feature? But I’m just guessing. You should request it and see what happens, maybe more people want it. I’ve never even thought about it, since in the case of Podman/docker it’s so “obvious” and easy to just mount network shares to the host first. And in the case of Kubernetes you can just mount NFS shares directly into pods.
“obviously”… dont get over yourself. theres been requests.plenty.
migration is also much easier. i think only edgelords prefer mouting in host and container.
Docker(/Compose) can do mounts directly to the container as well.
https://blog.stefandroid.com/2021/03/03/mount-nfs-share-in-docker-compose.html
https://docs.docker.com/engine/storage/volumes/#create-a-service-which-creates-an-nfs-volume
I’ve used NFS mounts with docker compose before but I see the second link also includes an example for CIFS as well.
I’m using UnRAID for storage and getting another Linux machine to mount a share on boot has been an exercise in futility so I get it.
Using nfs on ext4 file systems, I’ve always just added them to fstab and it works just like that
Yeah it definitely does not work in this case. Spent many hours online looking through threads of people with the same problems, but no real solution. I think it has something to do with Unraids MFS implementation. Might be a little older. Only way to get it to work is have a script run every 10 minutes to check for the drive and if it’s not mounted, mount it. Works well enough.
