It’s Never Too Late to Fix Your Versioning

Photo of numbers as on train station or airport departure/arrival boards.

For The Pragmatic Programmers, I shared the story of how I failed to fix a broken versioning scheme. A version number should be meaningful to users and other developers. If not, you need to correct that. You’re not locked into your current version scheme forever.

Many projects use Semantic Versioning (SemVer). SemVer is great for software that has a public API. But some projects can get by without it. “Compilation” projects (like Linux distributions) in particular can use date-based releases. No matter what you pick, it has to make sense. If it doesn’t, you owe it to yourself to switch to a scheme that makes sense.

This post’s featured image by Nick Hillier on Unsplash

Ben is a principal program manager at Red Hat, focused on the Fedora Project. He is the author of Program Management for Open Source Projects. Ben is an Open Organization Ambassador and frequent conference speaker. His personal website is Funnel Fiasco.

Leave a Reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.

%d bloggers like this: