

22·
6 months agoBasically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.


Basically, yes. Forces plugins not to use potentially database-engine-specific SQL so that server admins don’t have to select their DB based on plugins for jellyfin being compatible.


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.


While I appreciate that time zones change including dst… Your porch light shouldn’t care about dst, it should probably just care about actual light levels


Fwiw v clocks don’t need to have WiFi to auto adjust for dst. Just being date-aware and having a method to configure dst is all it takes.
“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