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.

all 3 comments

sorted by: hot top controversial new old
[–] 5 points 1 year ago (2 children)

Nice, looking forward to those ratings changes. The current rating system has a lot of discrepancies.

  • source
  • hideshow 2 child comments
  • [–] 5 points 1 year ago (1 child)

    Same here, the ratings for Australia are especially bad in the current system. Having PG, M and MA15+ all linked together probably makes sense if you've got no cultural context for it, but being from Australia it's an insane way to handle it haha

  • source
  • parent
  • hideshow 1 child comment
  • 10 comments in c/selfhosted@lemmy.world view that post
    [–] 12 points 1 year ago (1 child)

    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

  • source
  • hideshow 1 child comment
  • [–] 9 points 1 year ago

    The startup UI is a neat idea

  • source
  • [–] 14 points 1 year ago (6 children)

    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

  • source
  • hideshow 6 child comments
  • [–] [S] 16 points 1 year ago (2 children)

    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.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 7 points 1 year ago* (2 children)

    In traditional versioning systems you only jump major versions if you break compatibility with previous versions. For instance Semantic Versioning.

  • source
  • parent
  • hideshow 2 child comments