Jellyfin
Upgrading from 10.10.7 to 12.0.0 #16504
-
|
Like many others I am running the actually-stable pre-10.11 version of JF and check in from time to time to see the status of certain bugs/issues that deter me from upgrading. I have recently seen mention of a "12.0" release of JF. Will I be able to skip 10.11 completely or will I need to do a multi-stage upgrade due to DB migrations? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 7 replies
-
|
Skipping major releases is something we've never supported. It might work, but we recommend going to the latest 10.11 release before upgrading to 12.0. |
Beta Was this translation helpful? Give feedback.
-
|
A quick follow-up question - I'm still holding off upgrading from 10.10.7 until the majority of bugs have been fixed (as, I suspect, are many people). Will you be announcing when the last '11' version is deployed ? I get my code from linuxserver.io and therefore may suddenly find that the version downloaded via there is '12', thereby not allowing me to upgrade to '11' first. If I know a specific version is the last '11' version, then at least I know I have to download it when it's available before the '12' version is released. |
Beta Was this translation helpful? Give feedback.
-
|
No, we don't have a schedule or anything, so we don't know if the current 10.11.8 is the latest one or if there will be a 10.11.67 a day before 12.0 drops. |
Beta Was this translation helpful? Give feedback.
-
|
What bugs are holding you off from upgrading exactly? Initial 10.11 releases were extremely buggy, yes, I held off until the watch state on file renames was fixed 2 or 3 versions ago, but it has been laggy as fuck. Now everything works smoothly since 10.11.7, so unless you have any specific bugs that are holding you off, I'd say it's safe to upgrade to the current 10.11.8. |
Beta Was this translation helpful? Give feedback.
-
|
#15242 is the main one for me. I am going to experiment with the latest version and see how things go. I know I can't stay on v10 indefinitely! If all goes well, I'll try migrating. And if that works too then I'll consider upgrading my 'production' instance. Looking through the forum doesn't inspire confidence either: https://forum.jellyfin.org/t-new-jellyfin-server-web-release-10-11-7 "Shutdown my server, installed 10.11.7 over 10.10.7, waited, hoped, begged baby Jeebus.... JF server will not start now." #16062 seems to be an important one that won't come until v12 as well. I don't see a good reason to update. Security fixes should be backported if they affect 10.10.X (and if they are 10.11.X only then I avoided another forced update from 10.11.7 to 10.11.8). I don't want to sound ungrateful but rapid development on features is not a priority for everyone. |
Beta Was this translation helpful? Give feedback.
-
|
Most of these issues are isolated cases and do not affect most of the users. I, for instance, never experienced any of those bugs that you mentioned. As I said, the only thing holding me off was a functionality issue which has been fixed ever since (preserving watched state on file rename), and the only issue I faced after upgrading was a heavy cpu usage when rescanning the media library, which has been fixed since 10.11.7 as well. Test for yourself and don't rely on those isolated issues to hold off. |
Beta Was this translation helpful? Give feedback.
-
|
I just want to follow up and say that the upgrade process was really smooth for a library with about 15,000 items. Perhaps only 20-30 seconds. I'm not seeing any issues so far for a wide range of clients with and without transcoding. UI is more responsive and the delay to start a stream is almost imperceptible at times. |
Beta Was this translation helpful? Give feedback.
Skipping major releases is something we've never supported. It might work, but we recommend going to the latest 10.11 release before upgrading to 12.0.