• Phen@lemmy.eco.br
      27·
      7 days ago

      I wish it was true here. Major releases are always the most shameful ones because so much is always left to “we can fix that later”

      • NeatoBuilds@mander.xyzEnglish
        81·
        6 days ago

        Hey as long as it ships it can always be an RMA. If there’s a problem the customer will let us know™

    • MonkeMischief@lemmy.today
      3·
      5 days ago

      I’ve noticed this and seeing it all laid out is hilarious. (So, so many JS frameworks omg)

      Is this basically so they can forever say: “Well don’t expect it to be feature complete, it’s not even 1.0 yet!” ??

      • Ephera@lemmy.mlEnglish
        2·
        5 days ago

        I don’t think, it’s as conscious of a decision. Projects above a certain level of complexity will just never realistically reach the criteria one might associate with a 1.0 (stable API, no known bugs, largely feature-complete). And then especially non-commercial projects just don’t have an incentive to arbitrarily proclaim that they fulfill these criteria…

  • BakedCatboy@lemmy.mlEnglish
    31·
    6 days ago

    I once had someone open an issue in my side project repo who asked about a major release bump and whether it meant there were any breaking changes or major changes and I was just like idk I just thought I added enough and felt like bumping the major version ¯⁠\⁠_⁠(⁠ツ⁠)⁠_⁠/⁠¯

    • Rogue@feddit.uk
      24·
      6 days ago

      I think is the logic used for Linux kernel versioning so you’re in good company.

      But everyone should really follow semantic versioning. It makes life so much easier.

      • Swedneck@discuss.tchncs.de
        4·
        6 days ago

        either have meaning to the number and do semantic versioning, or don’t bother and simply use dates or maybe simple increments

        • Rogue@feddit.uk
          2·
          6 days ago

          Date based version numbers is just lazy. There’s nothing more significant about a release in two weeks (2025.x.y) than today (2024.x.y).

          At least with pride versioning there’s some logic to it.

          • Swedneck@discuss.tchncs.de
            2·
            5 days ago

            the point is just to have a way to tell releases apart, if every release is version 5 then you’re going to start self harming

  • luciferofastora@lemmy.zip
    5·
    5 days ago

    I use CalVer in my projects. I might transition to SemVer some time, but given that most of my projects are standalone, it doesn’t make much sense to track external compatibility.

    Pride Versioning makes no sense, because In never quite proud enough of my work to distinguish it from 0ver.

  • doktormerlin@feddit.org
    8·
    6 days ago

    I really had to fight for versioning. Everyone was just patch version here. Breaking changes in the API, new features, completely overhauled design? Well, it’s 0.6.24 instead of 0.6.23 now.

    But gladly we’re moving away from version numbers alltogether. Starting next year it will be 2025.1.0 with monthly releases