this post was submitted on 21 Jul 2023
57 points (100.0% liked)

linuxmemes

21263 readers
977 users here now

Hint: :q!


Sister communities:


Community rules (click to expand)

1. Follow the site-wide rules

2. Be civil
  • Understand the difference between a joke and an insult.
  • Do not harrass or attack members of the community for any reason.
  • Leave remarks of "peasantry" to the PCMR community. If you dislike an OS/service/application, attack the thing you dislike, not the individuals who use it. Some people may not have a choice.
  • Bigotry will not be tolerated.
  • These rules are somewhat loosened when the subject is a public figure. Still, do not attack their person or incite harrassment.
  • 3. Post Linux-related content
  • Including Unix and BSD.
  • Non-Linux content is acceptable as long as it makes a reference to Linux. For example, the poorly made mockery of sudo in Windows.
  • No porn. Even if you watch it on a Linux machine.
  • 4. No recent reposts
  • Everybody uses Arch btw, can't quit Vim, and wants to interject for a moment. You can stop now.

  • Please report posts and comments that break these rules!

    founded 1 year ago
    MODERATORS
     
    you are viewing a single comment's thread
    view the rest of the comments
    [–] ebits21@lemmy.ca -1 points 1 year ago* (last edited 1 year ago) (4 children)

    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.

    [–] jjjalljs@ttrpg.network 8 points 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.

    [–] FaeDrifter@midwest.social 7 points 1 year ago (1 children)

    How would you differentiate between versions with major api breaks?

    [–] bjornsno@lemm.ee 6 points 1 year ago (1 children)

    Shhh, they don't know what that means, let them live in bliss

    [–] ebits21@lemmy.ca 0 points 1 year ago (1 children)

    Lol. Developers just need to know what date the api changed. Viola.

    [–] bjornsno@lemm.ee 2 points 1 year ago* (last edited 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.

    They both serve different purposes

    KDE Plasma does its versioning to follow QT versioning, which does its versioning in that way to signify API breaks.

    But for something else like, say, the Linux kernel, which does not break compatibility in that manner, date-based would make more sense.

    [–] blackbelt352@lemmy.world 0 points 1 year ago (1 children)

    I really like X.Y.Z

    X is for major overhauls. Y is for a new individual feature added or dramatically reworked, Z is for bug fixes, updates and polish.

    Like Blender is currently on 3.6. They had a dramatic major program wide overhaul a few years ago. And since then have been adding new features and reworking old ones in major 3.X releases, and occasionally have smaller updates and fixes in between, giving us 3.X.Y updates.

    [–] BangersAndMash@lemmy.world -1 points 1 year ago (1 children)

    The only thing I don't like about that versioning system is the ambiguity that can sometimes arise due to different interpretations of what the numbers after the first dot mean.

    You could either say: It's a decimal system, therefore 3.4 is bigger (comes after) 3.13. (3.4 > 3.13) or, The numbers after each dot are independent, therefore 13 is bigger than 4, so 13 is the newer release.

    It's usually fairly obvious from changelings but every now and then I get tripped up.

    [–] blackbelt352@lemmy.world 3 points 1 year ago

    For versioning I always viewed the numbers as independent from each other, just like with ip addresses.