Firefox 132.0.1, See All New Features, Updates and Fixes
www.mozilla.org
  • fireshell@lemmy.mlEnglish
    5·
    17 hours ago

    As the release period was reduced to a month, so 0.1 0.2 0.3 began to appear and so every week

    • WhatAmLemmy@lemmy.worldEnglish
      4·
      14 hours ago

      I really prefer the Bitwarden approach to versioning, by including the date like YYYY.MM.DD.whatever. Makes it easy to know how old a version is at a glance, and easier to remember.

      • BleakBluets@lemmy.worldEnglish
        2·
        13 hours ago

        I prefer the SemVer Major.Minor.Patch approach so I can tell at a glance if the update breaks compatibility or is just bug fixes. Technically the Patch part can be any number as long as it increases each update of that same Minor version, so one could write the versions as AA.BB.YYMMXX where AA is the Major version, BB is the Minor, YY is the two digit year, MM is the month, and XX is just an incrementing number.

        I think this approach has the best of both systems.