this post was submitted on 28 Oct 2024
80 points (100.0% liked)
Firefox
20363 readers
19 users here now
/c/firefox
A place to discuss the news and latest developments on the open-source browser Firefox.
Rules
1. Adhere to the instance rules
2. Be kind to one another
3. Communicate in a civil manner
Reporting
If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Remember when a new major version meant something major changed?
Was nice as it prompted me to go read change notes. Now I have no clue when it's a collection of minor things or has actual major changes unless I go read every set of change notes.
And I wish they did follow semver, but loosely (i.e. major version bump shouldn't imply breakage, but instead a major new feature). If there is a major new feature, I think they should maintain security updates for the old one for some weeks in case there's a problem with the new feature.
That was the explicit goal of having huge irrelevant release numbers and to constantly release new versions: making sure nobody cares much and upgrade without much problems constantly to ensure security and web improvements are always there in users hands.
I remember the Firefox 2, 3 and 4 hype back in the day trying out the betas and waiting for the release. Since 5 though I stopped caring.
Now-a-days most of the (browser) software projects are following agile mode and not waterfall mode delivery.