Selfhosted

62002 readers

1575 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

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
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.
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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

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

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

536

Jellyfin 12 Released (github.com)

submitted 23 hours ago by Mountaineer@aussie.zone to c/selfhosted@lemmy.world

120 comments fedilink hide all child comments

cross-posted from: https://aussie.zone/post/36389875

Why jump from 10.11.11 directly to 12.0? -> Blog Post

You can find more details about and discuss this release on the official forums.

As always, please ensure you stop your Jellyfin server and take a full backup of your metadata/configs before upgrading!

Direct upgrades from 10.10.7 and 10.11.x to 12.0 are supported; intermediate upgrades are not required. Users running releases older than 10.10.7 are strongly encouraged to upgrade to 10.10.7 before migrating to 12.0.

Installed repository plugins (anything not built-in) should also be removed before migrating. Plugins will likely need time to adapt to the new database changes, so re-adding them afterward is the safest approach for testing.

Official plugins compatible with Jellyfin are available through the stable plugin repository. If you have changed to the unstable plugin repository please change it back.
Go to Dashboard -> Plugins -> Manage Repositories
Update the Plugin Repository URL to: https://repo.jellyfin.org/files/plugin/manifest.json
After migrating please perform the following steps.
Perform a full library scan to restore alternative versions
Run the "Optimize database" scheduled task
___

you are viewing a single comment's thread
view the rest of the comments

[–] TheOctonaut@piefed.zip 46 points 21 hours ago (2 children)

The reason is the feedback we got after 10.11.0, which we first raised in January and confirmed in May. A release like 10.11.0 was, by any reasonable measure, a major release - it rewrote the library database - but the version number presented it as a minor update, and people upgraded with expectations to match. The leading 10. never changed and never told anyone anything, so all it did was push the number that actually mattered into the middle position and make "major" releases look minor. Dropping it means the first number moves when the release is big.

lol. All the Jellykins in here lost their minds when this was pointed out.

[–] samc@feddit.uk 19 points 19 hours ago (2 children)

I dont get why they didn't just call that update 11.0? Or use that for this update?

I guess if you're changing the semantics of your version numbers its also a good idea to introduce a deliberate discontinuity to mark the change?

[–] CHOPSTEEQ@lemmy.ml 10 points 15 hours ago

I was confused too, but I guess their logic is that 10.11.x is 11.x.x. They might have been more explicit about that.

[–] BooBees@fedinsfw.app 14 points 18 hours ago

This one goes 1 more than 11

[–] Axolotl_cpp@feddit.it 6 points 15 hours ago

My guess is that people would call the 10.11.x update something like .11.x instead of the full version because "they don't change the first number anyway" and it would cause confusion to call the next update version 11.x.x so they just jumped to 12