• Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below
  • Forum
  • Website
  • GitHub
  • Status
  • Translation
  • Features
  • Team
  • Rules
  • Help
  • Feeds
User Links
  • Login
  • Register
  • Login Register
    Login
    Username/Email:
    Password:
    Or login with a social network below

    Useful Links Forum Website GitHub Status Translation Features Team Rules Help Feeds
    Jellyfin Forum Off Topic General Discussion Upgrades

     
    • 0 Vote(s) - 0 Average

    Upgrades

    Discussion about upgrade process
    enesha
    Offline

    Member

    Posts: 58
    Threads: 16
    Joined: 2023 Nov
    Reputation: 1
    Country:United Kingdom
    #1
    2025-11-23, 11:00 PM
    Good Evening all

    Just here to start a discussion about upgrades.  The way that things happen for Jellyfin needs to change!

    10.10 from 10.9 was a fiasco

    10.11 from 10.1.x is a total SH*T Show!

    The release was announced on a Blog post.  A friggin blog post.  I come on here sometimes and didn't see anything about an upgrade of the apparent year the devs said this too.  6+ months for dev and 6+ months for rc testing..Never heard a damn thingf.

    The upgrade and the warning were announced on the blog.  Big warning on the blog for critical info.  Specific versions to upgrade from..,.leave running...All things that are super important but included in a friggin blog post.

    Then the upgrade rolls out.  A lot of places, the various nix'es  and dockers can auto update themselves, and do...with no regard to Major versions.

    This is not new.  When there is such a massive and import upgrade, maybe the server itself could warn us a new version is here should we do X

    Blindisding people with this sort of thing is just unacceptable. I know you guys are unpaid, and I assume this is a labor of love, but we need to make some changes here.

    Just look around and see the issues that people have.  Read the reddits, read the forums, it's screwing people up!  This is not a small issue.

    We need people to be forewarned about things!  A post-it note on a blog just isn't good enough.

    Sorry to rant, but this is pissing me the f off today!
    Intel® Core™ i7-14700 @ 5247 MHz 
    Official Docker
    ~200 tb raid
    FullSubstance7196
    Offline

    Junior Member

    Posts: 4
    Threads: 0
    Joined: 2025 Nov
    Reputation: 0
    #2
    2025-11-23, 11:39 PM
    Uhhh... Every channel that Jellyfin uses for communications had the release announcement.
    It was on the forums, on the blog post, on github, on Matrix, on Discord, etc.
    1
    www.com.au
    Offline

    Junior Member

    Posts: 6
    Threads: 0
    Joined: 2023 Dec
    Reputation: 0
    Country:Australia
    #3
    2025-11-25, 12:42 AM
    I saw the update announcement via reddit, but I get where you are coming from, most people just aren't going to go check the forums or discord everytime there's an update, so an in-app warning would be ideal.
    TrueCodePoet
    Offline

    Junior Member

    Posts: 7
    Threads: 1
    Joined: 2025 Feb
    Reputation: 0
    #4
    2025-12-05, 11:19 PM
    (2025-11-23, 11:00 PM)enesha Wrote: Good Evening all

    Just here to start a discussion about upgrades.  The way that things happen for Jellyfin needs to change!

    10.10 from 10.9 was a fiasco

    10.11 from 10.1.x is a total SH*T Show!

    The release was announced on a Blog post.  A friggin blog post.  I come on here sometimes and didn't see anything about an upgrade of the apparent year the devs said this too.  6+ months for dev and 6+ months for rc testing..Never heard a damn thingf.

    The upgrade and the warning were announced on the blog.  Big warning on the blog for critical info.  Specific versions to upgrade from..,.leave running...All things that are super important but included in a friggin blog post.

    Then the upgrade rolls out.  A lot of places, the various nix'es  and dockers can auto update themselves, and do...with no regard to Major versions.

    This is not new.  When there is such a massive and import upgrade, maybe the server itself could warn us a new version is here should we do X

    Blindisding people with this sort of thing is just unacceptable. I know you guys are unpaid, and I assume this is a labor of love, but we need to make some changes here.

    Just look around and see the issues that people have.  Read the reddits, read the forums, it's screwing people up!  This is not a small issue.

    We need people to be forewarned about things!  A post-it note on a blog just isn't good enough.

    Sorry to rant, but this is pissing me the f off today!

    just want to say that I understand where you’re coming from. I’ve been a software developer for 30 years, so I appreciate the amount of work that goes into this. That said, this release has been an absolute nightmare. It honestly feels like it should have been a separate product altogether.

    I pulled the source down a while back and have had ideas about improving it. I keep asking myself at what point I should just fork it to meet my own needs. The search still performs poorly, the database is a mess, and the overall experience is wearing thin. I know it’s open source, but even the Roku app rollout broke support for the legacy server and only today did I learn there’s a separate app for that.

    The level of effort required to keep things running now makes it feel like I’d be better off taking ownership myself. With AI, I could run a few agents and implement updates far more quickly. It’s been a rough day, and this chaos has caused me more frustration than I expected.  I am almost venting more than anything.  Basically the whole experience is slow and almost unusable unless I am using the web browser.  This post just expressed my frustrations also.  I guess I just expected something a little more reasonable.  This was just not ready.  To soon.
    TCTC
    Offline

    Junior Member

    Posts: 1
    Threads: 0
    Joined: 2025 Dec
    Reputation: 0
    Country:United States
    #5
    2025-12-07, 07:55 PM
    An additional suggestion on the topic, the upgrade script could be made sufficiently smart to NOT kill a working installation.

    Until today, I had a working, but older, Jellyfin installation. I became aware that a newer release was available, and found the following installation command at https://jellyfin.org/downloads/server/;

    curl -s https://repo.jellyfin.org/install-debuntu.sh | sudo bash


    That seemed official, and I naively assumed that it would be safe, so I ran it.

    Now I have zero Jellyfin installations, because that has rendered my previously-working installation, dead. Suggest that it is likely possible to add a check to that script to prevent this from occurring. At a minimum,
    a warning to the user to check their installed version, and ensure that it is sufficiently-recent to allow upgrading to the current release, would be friendlier than silently clobbering.
    « Next Oldest | Next Newest »

    Users browsing this thread: 1 Guest(s)


    • View a Printable Version
    • Subscribe to this thread
    Forum Jump:

    Home · Team · Help · Contact
    © Designed by D&D - Powered by MyBB
    L


    Jellyfin

    The Free Software Media System

    Linear Mode
    Threaded Mode