• ebits21@lemmy.ca
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    1 year ago

    Everything should be date-based name releases.

    If it’s released April, 2023 it should be 23.04 or similar.

    Other schemes are arbitrary.

    Change my mind.

          • bjornsno@lemm.ee
            link
            fedilink
            arrow-up
            1
            ·
            edit-2
            1 year ago

            Gotta know, are you serious or joking here? Follow up question: are you a developer and have you ever worked on a medium+ sized project? The amount of dependencies you end up with is astounding, you can’t just “know” when all those APIs changed, that would be a full time job just to stay on top of. And that’s not even taking into consideration transitive dependencies. If a library doesn’t use semantic versioning, 99% of the time it’s correct to avoid it just to save yourself the headache.

    • jjjalljs@ttrpg.network
      link
      fedilink
      arrow-up
      1
      ·
      1 year ago

      Semantic versioning. If I have 1.0.0 and you release 1.1.0 I can be pretty confident it’s safe to update. If you release 2.0.0 I need to read the release notes and see what broke.

      If I have version July2023 and you release August2023 I have no information about if it’s safe to update. That’s terrible. That’s really bad.

      This is for dependency management and maybe apis more than OSs, but in general semantic versioning is a very good system. It should be used often.