• SorteKanin@feddit.dk
    link
    fedilink
    English
    arrow-up
    0
    ·
    9 months ago

    There was a big time gap between 0.18.5 and 0.19. Have you considered adopting a release train model, similar to what Rust does? The Bevy game engine has also adopted the idea.

    More frequent but smaller releases would probably cause less friction and make upgrading less of a “big thing” and “big things” are always things go wrong.

    • TheAnonymouseJoker@lemmy.ml
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 months ago

      I would argue the Chrome style release model aka rushing for version numbers is what created the developmental mess in tech industry. It demands unnecessary effort and creates a lot of stress, and is a huge symptom of the capitalist market disease. There is no innovation in chasing new version numbers.

    • 1984@lemmy.today
      link
      fedilink
      English
      arrow-up
      0
      ·
      edit-2
      9 months ago

      They normally do have smaller releases (18.1, 18.2, 18.3, 18.4, 18.5) but going from 18 to 19 was a big update that also required a database upgrade. Rust releases don’t have database upgrades or anything that is not backwards compatible, so it’s not really comparable.

    • phiresky@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      9 months ago

      0.19 was a bit of a special case because there was a set of breaking updates that had to be done at some point, and trickle releasing breaking changes isn’t really great either. Usually hopefully the breaking changes are rare, so releases can be more frequent.