Firefox 132.0.1 Release Notes (www.mozilla.org)

submitted 2 weeks ago by hal_5700X@sh.itjust.works to c/firefox@lemmy.ml

14 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[-] WhatAmLemmy@lemmy.world -1 points 2 weeks ago

I would never trust a dev defined SemVer as more than a relatively useless indicator of compatibility. I make sure there's proper unit and integration testing to prevent external dependencies breaking production. If it's a major dependency I check the release notes every version.

[-] sugar_in_your_tea@sh.itjust.works 1 points 2 weeks ago

Eh, I'd much rather have a dev-defined SemVer that's sometimes inaccurate than something that just arbitrarily increases every release. The first provides some information, the second doesn't.

[-] BleakBluets@lemmy.world 1 points 2 weeks ago

My suggestion is in compliance with standard SemVer as far as I can tell, but yes it is frustrating when apps use versioning that looks like SemVer, but make interface changes in Minor versions and don't really adhere to SemVer.

this post was submitted on 05 Nov 2024

57 points (98.3% liked)

Firefox

17302 readers

2 users here now

A place to discuss the news and latest developments on the open-source browser Firefox

founded 4 years ago

MODERATORS

k_o_t@lemmy.ml