IGNITE: Did Anyone Say SemVer?

on YouTube ↗08m

" summary

Semantic Versioning is common but inconsistent: SemVer itself is at 2.0.0 and pre-1.0 is basically zerover where anything goes; the core dispute is what counts as an API (REST endpoints, OS support, UI changes) so fixes can silently break someone’s workflow. Real projects diverge: Kubernetes uses deprecation and a rolling forward policy instead of frequent majors, Java does time-based majors on a six‑month cadence, Terraform made breaking changes in 0.x, MySQL jumped majors for nontechnical reasons, and Ubuntu uses calendar versioning.

AI-written summary · about

" related talks

• 30mPutting the Semantics into Semantic VersioningPatrick Lam, Jens Dietrich, David J. Pearce · SPLASH 2022
• 15mPutting the Semantics into Semantic VersioningPatrick Lam, Jens Dietrich, David J. Pearce · Onward! 2020
• 16mLightning Talk - Automating SemVer for Fun and Profit: ...Andrew Goode · npm camp 2016
• 32mReleasing Calendar-Versioned SoftwareAmber Brown · PyCon AU 2016
• 30mNavigating the Multi-Version Kubernetes Universe: How Emulation Version Shapes Your...Siyuan Zhang · CNCF Maintainer Summit North America 2025
• 34mPolicy As [Versioned] CodeChris Nesbitt-Smith · Critical Software Summit @ Open Source Summit Europe 2022
• 40mBackwards Incompatible TalesMarco Pivetta · Dutch PHP Conference 2019
• 16mWhy Is My Software on Fire?Laurent Goderre · SOSS Fusion 2024