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
Search - "versioning scheme"
-
Longtime reader, first time ranter!
I'm just here to complain about how everyone at my company sets "latest" for every dependency.
This wouldn't be the worst thing in the world, expect that no one fucking manages their version numbers...everything is still 1.0.X where X is the build number. Even if there have been breaking changes. Even if it's been like 5 years since the repo was created... -
Long time ago I worked with a few developers on some relatively simple web project. We were using php and smarty and we used svn for versioning. At one point some dude joined the project as a php developer (with a few years of experience).
After a few days without any commits, we found out that he doesn't know what a SVN is or how to use it. After he learned how to use it we found out in our repo bunch of files with a following naming scheme:
filename.php
filename_1.php
filename_2.php
filename_3.php
filename_4.php
filename_5.php -
Angular 5 was just released! *Yay*
on a completely unrelated note: does anyone get the versioning/naming scheme of angular?8 -
When I said: "version numbers are cheap", I did not expect you to append new digits and identifiers to the existing versioning scheme.