Comment on New Jellyfin Server/Web release: 10.10.7
jonne@infosec.pub 3 days agoI mean, it’s patching a security issue caused by trusting headers it shouldn’t, so I don’t think they should wait for a big number release.
Comment on New Jellyfin Server/Web release: 10.10.7
jonne@infosec.pub 3 days agoI mean, it’s patching a security issue caused by trusting headers it shouldn’t, so I don’t think they should wait for a big number release.
sugar_in_your_tea@sh.itjust.works 3 days ago
Why wait? Just release it as a big number release. The version number doesn’t define the size or cadence of a release, it just says whether there’s a breaking change.
mac@lemm.ee 3 days ago
At least in my org we use semantic versioning ( Major.Minor.patch) where patch must either be a new feature, a fix, or something that is backwards compatible
Rogue@feddit.uk 2 days ago
That’s not semantic versioning…
mac@lemm.ee 1 day ago
Guess my org fucked it up ¯\(ツ)/¯