523
top 28 comments
sorted by: hot top controversial new old
[-] beeng@discuss.tchncs.de 14 points 16 hours ago
[-] lord_ryvan@ttrpg.network 7 points 12 hours ago

I'm afraid most, if not all, of the projects listed use pride versioning, also.

[-] AnActOfCreation@programming.dev 2 points 11 hours ago

This is hilarious

[-] doktormerlin@feddit.org 6 points 16 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

[-] BakedCatboy@lemmy.ml 33 points 1 day 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 points 1 day 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 3 points 9 hours 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 points 9 hours 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.

[-] avidamoeba@lemmy.ca 60 points 1 day ago* (last edited 1 day ago)

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

[-] Rogue@feddit.uk 2 points 9 hours ago

For an internal project that's fine, and under semantic versioning you can basically break anything you like before v1.0.0 so it's probably valid

[-] lord_ryvan@ttrpg.network 4 points 12 hours ago

A shameful display!

This is is basically just true

[-] Phen@lemmy.eco.br 23 points 1 day 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.xyz 8 points 1 day ago

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

[-] fmstrat@lemmy.nowsci.com 3 points 1 day ago

So pride is a synonym for semantic. Got it.

[-] Outdoor_Catgirl@hexbear.net 35 points 1 day ago

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

[-] davel@lemmy.ml 13 points 1 day ago

Pride versioning:

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

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

[-] QuazarOmega@lemy.lol 14 points 1 day ago

The + is just standing for latest

[-] swab148@lemm.ee 5 points 18 hours ago
[-] sudoer777@lemmy.ml 3 points 17 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 17 hours ago

Lmao yes
Arch and queer, name a better duo

[-] buh@hexbear.net 40 points 1 day ago

when the release notes just says "bug fixes"

[-] propter_hog@hexbear.net 31 points 1 day ago
[-] Swedneck@discuss.tchncs.de 3 points 9 hours ago

"We are always hard at work making your experience better!"
This release note has of course been the same for the last 3 years

[-] davel@lemmy.ml 13 points 1 day ago

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 1 day ago
[-] akkajdh999@programming.dev 13 points 1 day ago

Thought it's 2.7.1828182845904523536 for a sec

this post was submitted on 21 Dec 2024
523 points (99.6% liked)

Programmer Humor

32707 readers
744 users here now

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

Rules:

founded 5 years ago
MODERATORS