Happy New Year and welcome to the State of the Fin! This new blog series will regularly basis highlight the ongoing development of Jellyfin and our official clients. We aim to keep our community informed and engaged, so feel free to share your feedback or thoughts on our progress!
December marked Jellyfin's 7th anniversary! A lot has changed in 7 years, but we remain steadfast in our commitment to Open Source and to being the best personal media server out there. Special thanks to our developers, testers, moderators, and supporters for your invaluable contributions! Here's to many more years of collaboration and streaming!
We received a substantial amount of feedback regarding our versioning scheme following the 10.11 release, particularly concerning the stability of what are perceived as 'minor' version updates. This has prompted internal discussions about potentially revising our versioning scheme in the next major release. While nothing has been finalized yet, we are considering 'dropping' the major version 10, which would make the next release 12.0. Stay tuned for further updates as we navigate this feedback!
Jellyfin 10.11 introduced a major EF Core refactor, consolidating the legacy library.db into a single unified jellyfin.db . Following more than six months of development and an additional six months of release candidate testing, version 10.11.0 was released last year. This extended testing period allowed us to mitigate most refactoring and RC-related issues prior to release.
Even with this level of testing, issues were expected given the scale of the database change and the limited number of users reporting bugs. These issues are currently being tracked on GitHub across three categories:
We have been moving quickly to address these issues, delivering four additional point releases with over 100 changes since the initial 10.11.0 release. To date, most point releases have focused on resolving general and migration-related issues. The remaining migration issues are largely isolated, one-off cases and are unlikely to be resolved. Most general issues have already been fixed, and the next bug-fix release is expected to include additional fixes for music metadata display issues and for watched status not being preserved when media is replaced or renamed.
We are continuing to investigate ways to mitigate performance issues caused by client-side enumeration and filtering of large datasets.
Default 'Experimental' Layout : The 'Experimental' layout is now enabled by default for all non-TV devices, introducing a new navigation layout and updated UI components.
: The 'Experimental' layout is now enabled by default for all non-TV devices, introducing a new navigation layout and updated UI components. Theming Support Overhaul : We are improving theming support by enabling easier runtime customization of default themes through CSS variables and simplifying the process for creating new bundled themes.
: We are improving theming support by enabling easier runtime customization of default themes through CSS variables and simplifying the process for creating new bundled themes. Community Acknowledgment: Huge thanks to those reviewing, testing, and providing feedback on web pull requests. Your contributions are immensely helpful, as the review burden largely falls on me alone!
... continue reading