this post was submitted on 21 Dec 2024
428 points (99.5% liked)

Programmer Humor

32716 readers
657 users here now

Post funny things about programming here! (Or just rant about your favourite programming language.)

Rules:

founded 5 years ago
MODERATORS
 
top 21 comments
sorted by: hot top controversial new old
[–] doktormerlin@feddit.org 1 points 2 hours 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

[–] beeng@discuss.tchncs.de 2 points 2 hours ago
[–] BakedCatboy@lemmy.ml 25 points 13 hours ago (1 children)

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 16 points 12 hours 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.

[–] Outdoor_Catgirl@hexbear.net 30 points 15 hours ago (1 children)

I read this as pride as in flag-gay-pride

[–] davel@lemmy.ml 11 points 13 hours ago (2 children)

Pride versioning:

  • LG
  • LGB
  • LGBT
  • LGBTQ
  • LGBTQI
  • LGBTQIA
  • LGBTQIA+

Is + when they stop counting versions and just use a SaaS model?

[–] QuazarOmega@lemy.lol 10 points 12 hours ago (1 children)

The + is just standing for latest

[–] swab148@lemm.ee 5 points 4 hours ago (2 children)
[–] sudoer777@lemmy.ml 3 points 3 hours ago

I prefer LGBTQIA-bin, my computer was in the closet for 10 years so the git version takes too long to compile

[–] QuazarOmega@lemy.lol 3 points 3 hours ago

Lmao yes
Arch and queer, name a better duo

[–] avidamoeba@lemmy.ca 51 points 17 hours ago* (last edited 17 hours ago)

The fairly mature internal component we're working on is v0.0.134.

[–] Interstellar_1@lemmy.blahaj.zone 61 points 18 hours ago (2 children)

This is is basically just true

[–] fmstrat@lemmy.nowsci.com 3 points 10 hours ago

So pride is a synonym for semantic. Got it.

[–] Phen@lemmy.eco.br 17 points 16 hours ago (1 children)

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.xyz 8 points 15 hours ago

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

[–] buh@hexbear.net 36 points 17 hours ago (1 children)

when the release notes just says "bug fixes"

[–] propter_hog@hexbear.net 28 points 16 hours ago

"Various improvements"

[–] davel@lemmy.ml 13 points 17 hours ago (1 children)

That reminds me, maybe I should re-watch Doug Hickey’s full-throated attack on versioning & breaking changes. Spec-ulation Keynote

[–] yogthos@lemmy.ml 6 points 17 hours ago
[–] akkajdh999@programming.dev 13 points 17 hours ago

Thought it's 2.7.1828182845904523536 for a sec