• kennebel@lemmy.world
    link
    fedilink
    arrow-up
    40
    arrow-down
    2
    ·
    4 months ago

    That is 100% up to every team to decide. Version numbering is completely arbitrary.

    • DirigibleProtein@aussie.zone
      link
      fedilink
      arrow-up
      25
      ·
      edit-2
      4 months ago

      Since version 3, TeX has used an idiosyncratic version numbering system, where updates have been indicated by adding an extra digit at the end of the decimal, so that the version number asymptotically approaches π. This is a reflection of the fact that TeX is now very stable, and only minor updates are anticipated. The current version of TeX is 3.141592653

    • Cirk2@programming.dev
      link
      fedilink
      arrow-up
      8
      ·
      4 months ago

      I wish. Sadly the google play store requires monotonically increasing build numbers, so any option of resetting build numbers after major releases goes out the window.

      • maynarkh@feddit.nl
        link
        fedilink
        arrow-up
        5
        ·
        4 months ago

        Do Google engineers get off on writing software that’s only compatible within their own little world, then offering it as some de facto standard?

        Google Cloud had a ton of these that make it arbitrarily hard to use.

    • AggressivelyPassive@feddit.de
      link
      fedilink
      arrow-up
      5
      ·
      4 months ago

      I had lengthy discussions about that because two companies conventions collided.

      We talked literally hours about the benefits of build numbers, branch specific identifiers and so on.