#Semanticversioning
Forget semantic versioning, use PRIDE VERSIONING! 🏳️‍🌈
pridever.org

#semver #SemanticVersioning #programming #ProgrammTipp #programmer_humor #version #dev #development
Pride Versioning - Pride Versioning 🏳️‍🌈 0.2.0
Forget semantic versioning, use PRIDE VERSIONING 🏳️‍🌈
pridever.org
December 22, 2024 at 10:30 AM
Une proposition intéressante d'ajouter une notion supplémentaire au *Semantic Versioning* pour distinguer les "simples" breaking changes des changements plus conséquents.

L'intérêt de cette approche est qu'elle reste compatible…

🔗 https://links.kalvn.net/shaare/vSXRxw

#version #SemanticVersioning
kalvn's links
links.kalvn.net
January 7, 2025 at 10:25 PM
Ich habe Claude Code angewiesen, Semantic Versioning für mein Projekt anzuwenden. Nun diskutiere ich mit ihm/ihr/es, ob etwas ein Bug oder ein Feature ist… Manche Dinge ändern sich nie! :blobsmilesweat:

#vibecoding #requirements #ai #learning #semanticversioning #softwaredevelopment […]
Original post on freiburg.social
freiburg.social
July 29, 2026 at 8:08 AM
One of the things that #Emberjs & it's ecosystem does (mostly) correctly wrt/ #semanticversioning is:

✅ Major versions are for breaking changes.
❌ Major versions are for adding fancy new features.

It looks weird and less shiny at first, but let me reassure you: Once you start maintaining any […]
Original post on mastodon.world
mastodon.world
January 12, 2026 at 1:43 PM
Neu im Blog:
Versionsnummern in TYPO3 und Extensions: Dein Shortcut zu besserer Planung
https://buff.ly/3ZOzUDX

#SemanticVersioning #TYPO3 #SoftwareUpdates
December 23, 2024 at 9:10 AM
Made me smile: "Viele Projekte bleiben jahrelang unter 0.x und haben dann Angst vor 1.0. — Das bringt nichts außer Unsicherheit." #semanticversioning
January 10, 2026 at 10:20 AM
The "finger and toe rule"
Linus once joked that he can count version numbers on his fingers and toes, so:

He’s comfortable counting up to 20 (10 fingers + 10 toes)
6.19 -> 7.0

#VersionControl #SoftwareDevelopment #SemanticVersioning #CodingHumor #TechJokes #Versioning #DevLife
February 7, 2026 at 7:20 PM
with static analysis, clear contribution guidelines, thorough documentation, proper test coverage, a well-defined #branchingstrategy, #SemanticVersioning, and a build pipeline that can be tested and adopted locally. The service hosting the source (cont'd)
October 22, 2024 at 2:06 PM
It all depends on the quality of the package. Does the author follow #SemanticVersioning so you can understand the implications of the update? Are there any known issues with the new version from the community? (cont'd)
October 15, 2024 at 5:22 AM
Next, always apply #SemanticVersioning. It’s a simple system: increment the major version for breaking changes, the minor version for new features, and the patch version for bug fixes. (cont'd)
October 10, 2024 at 5:24 PM