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
-
Ah, I retract my rant. semver.org specifies that all requirements for versioning only apply if the major version is not 0.
So I may as well use
0.1.0 to denote a breaking change
0.1.1 to denote a new feature
Even though
1.0.0 declares a breaking change
1.1.0 denotes a new feature
1.1.1 denotes a bug fix
When starting projects, following semver.org quickly gets out of hand. Nothing is "backwards-compatible"
0.0.0 gitignore
0.1.0 prints arguments
1.0.0 prints text of web requests
2.0.0 prints parsed web requests
3.0.0 prints filtered requests
4.0.0 prints using yaml
5.0.0 logs to file
5.0.1 catch error
5.1.0 interactive
undefined