• sugar_in_your_tea
    link
    fedilink
    arrow-up
    3
    ·
    9 months ago

    Yes, you’d have to change the definition of a major release from “breaking change” to “big change.” Your normal releases would increment the minor version, security fixes would increment the patch version, and big changes would increment the major. Whether something is “big” is pretty subjective, but they provide an opportunity for marketing.

    Or if we want to go with something objective and simple, the major release would correspond to an ESR release, which happens about once/year.

    The purpose here is to make the numbers mean something rather than “number goes up.” If you ask me what was in Firefox 120, I would have no idea because large numbers are harder to remember than smaller numbers.

    • ahal@lemmy.ca
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      Yeah it could work too. Like you said though it’s subjective and internal arguments about what deserves to be big or not sounds tiring :p. For marketing large changes, inventing a buzzword seems to be working well enough.

      I guess to each their own, but I kind of like not knowing the version. I just use Firefox and if I really care what’s new I can look at the changelog, or see it in the what’s new pop-up.