Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
Please send him a link to semver and ask him to memorize it if she/he ever wants to be taken seriousely
https://semver.org/
Otherwise change version to be "1-800-alpaka-boss/5.5" -
@bioDan I'm thinking about some kind of Ubuntu Release model.
21.10 Moronic Manager
22.04 Embarrassing Executive
22.10 Cunty Coworker
23.04 Jerky Junior
23.10 Stubborn Stakeholder
🤷♀️ -
Meh. And it's so simple.
First digit its the version number, only changes if the program changes completely (or you make a new version from scratch)
Second number only changes when features are added / removed
Third number is for bug fixes.
Alfas, betas and anything starting with 0 are prototypes (the client won't see any until the first number is a 1) -
@GyroGearloose tell that to my side project version 0.9.64567434753
My biggest pet peeve at the moment is people without any development experience using version numbers.
Me: "Communicating a release date for the feature towards clients is dangerous, we have a developer shortage, and currently don't really have enough capacity to..."
Manager: "What we release next month doesn't have to be perfect, it is just a v1"
Me: "You mean it's a beta? If that's the case, could you maybe differentiate the requirements of the beta, let's call it a 0.1.0, versus the 1.0.0-rc, the release candidate?"
*Feature is eventually merged into production, barely in a beta state*
Manager: "So I have some ideas for the v2"
Me: "You mean 1.0.0"
Manager: "Let's compromise and call it v1.5"
Me: "Let's compromise, you stop communicating release dates, AND you stop using version numbers..."
Manager: "That's not a compromise..."
Me: "...I wasn't finished... And I won't respond to the recruiter who just offered me a better paying job"
rant