this post was submitted on 21 Jul 2023
657 points (98.0% liked)

linuxmemes

21263 readers
913 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
    [โ€“] [email protected] 20 points 1 year ago (1 children)

    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.

    [โ€“] [email protected] 2 points 1 year ago

    Alright I think I saw been somewhat convinced by this. But I also think the date should be included in some way.