Comments (1)
Laravel didn't start using SemVer until version 6, so version 4 didn't have to follow the MAJOR.MINOR.PATCH system
And I don't say the opposite as I say in the page you cited:
I use Laravel Framework professionally in a daily base, so I will use it as example to show as one that does not follow the SemVer version schema, or if you prefer, it works around it when needs to release changes that are Backwards Incompatible.
Well it seems that my above sentence and by the same reasoning the entire document can have a different interpretation, as per your conclusion:
So what does this tell me? It tells me the "WHY" is wrong and the entire premise is flawed. To solidify the reason why anyone would want to move away from SemVer, you should find an example of where SemVer actually fails in its own protocols, and you haven't demonstrated this.
So I stand by what I wrote and the premises are not wrong at all, but you and everyone else is free to disagree and/or have their own interpretations of my words, because that is out of my control ;)
Our industry is famous to stick with bad decisions from the past, just because they are already there for sometime, and some fiercely defend them while others try to find better alternatives, while other don't care if it goes one way or the other ;)
As a side-note, your "Disruptive" vs "Breaking" versions really don't add much, since a breaking backwards-incompatible change would, by definition, always be disruptive to the user.
As with anything else words can have always different meanings and interpretations, depending on each individual, but at least the ones used in Explicit Versioning are more explicit than the ones used in SemVer.
One thing strikes me as awkward, but again, I'm not invested at all in this versioning system so this is just me playing devil's advocate.
Thanks for your feedback :)
Once you are not invested in this Explicit Versioning system then I think is pointless to keep an ongoing discussion about all the possible interpretations that my sentences can have, and the last thing I want to start here is a flame war about SemVer vs Explicit Versioning.
from explicit-versioning.
Related Issues (9)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from explicit-versioning.