• BombOmOm@lemmy.world
    link
    fedilink
    English
    arrow-up
    20
    arrow-down
    5
    ·
    1 day ago

    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.

    • Karna@lemmy.mlOP
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      24 hours ago

      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.

      Now-a-days most of the (browser) software projects are following agile mode and not waterfall mode delivery.

    • Quail4789@lemmy.ml
      link
      fedilink
      English
      arrow-up
      8
      arrow-down
      2
      ·
      1 day ago

      Firefox doesn’t follow semver so these aren’t major releases. It’s a user-facing app not a library.

      • sugar_in_your_tea@sh.itjust.works
        link
        fedilink
        arrow-up
        9
        ·
        edit-2
        1 day ago

        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.

    • devfuuu@lemmy.world
      link
      fedilink
      arrow-up
      7
      arrow-down
      1
      ·
      1 day ago

      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.