197
Jellyfin 10.11 RC1 Released (github.com)
submitted 1 year ago by to c/selfhosted@lemmy.world
38 comments fedilink hide all child comments
 

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
[–] 12 points 1 year ago (6 children)

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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 6 child comments
    •
  • [–] 24 points 1 year ago (2 children)

    Their reasoning is literally the second sentence on that page.

    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, at some point, with previous Emby-compatible interfaces, and may also break compatibility with previous 10.Y releases 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 11 points 1 year ago* (last edited 1 year ago) (1 child)

    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?

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 6 points 1 year ago

    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.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 8 points 1 year ago (2 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.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] -1 points 1 year ago (1 child)

    "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

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 1 point 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.

  • permalink
  • fedilink
  • source
  • parent