Comment on Jellyfin 10.11 RC1 Released
dgdft@lemmy.world 1 year ago
Is there a buried lede here? What’s noteworthy about an RC of a minor version release?
I’m serious, there’s so much lazy posting on Lemmy regarding software releases.
Jellyfin is quite a big name, but still, the pattern is clear.
sj_zero 1 year ago federation: unsentI 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.
ddash@lemmy.dbzer0.com 1 year ago 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.
exu@feditown.com 1 year ago 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. jellyfin.org/docs/general/…/release-procedure/
Claims to follow semantic versioning, explicitly mentioning changes to plugin APIs as reasoning for a new major version.
exu@feditown.com 1 year ago 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 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.
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?
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!
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. 👍
Untold1707@lemmy.zip 1 year ago
Sorry, I didn’t realize some Lemmy clients don’t show cross-post descriptions. I’ll copy past it below:
WIP release notes: 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.
victorz@lemmy.world 1 year ago
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.