this post was submitted on 09 Jun 2025
204 points (98.1% liked)

Selfhosted

61451 readers
387 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

  1. Be civil.

  2. No spam.

  3. Posts are to be related to self-hosting.

  4. Don't duplicate the full text of your blog or readme if you're providing a link.

  5. Submission headline should match the article title.

  6. No trolling.

  7. Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.

  8. AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago
MODERATORS
 

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 are viewing a single comment's thread
view the rest of the comments
[–] ShortN0te@lemmy.ml 8 points 1 year ago (1 children)

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.

[–] stevestevesteve@lemmy.world -1 points 1 year ago (1 children)

"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

[–] ShortN0te@lemmy.ml 1 points 1 year ago

... 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.