4 ms·
I think the key flaw is that some people just don't like incrementing the major version number! It's a simple as that.
by chrisseaton 8y ago
I think the key flaw is that some people just don't like incrementing the major version number! It's a simple as that.
- bobwaycott 8y agoAre you bemoaning the lack of backward incompatible changes, or the lack of major version numbers because it feels like progress?
- chrisseaton 8y agoI'm not bemoaning anything, mate. I'm saying other people bemoan it. If you want to know why you'll have to ask them.
- bobwaycott 8y agoNo problem. It remains unclear how other people not wanting to increment a major version is SemVer’s key flaw. Perhaps you could have worded that better?
- chrisseaton 8y agoIf people don't want to use SemVer because they don't like incrementing the major component then that's a fundamental flaw. There's no point in it if it's not being used. There's already a few examples of people's attitudes in sibling comments. > Perhaps you could have worded that better? That's a bit snide.
- bobwaycott 8y ago> That's a bit snide. I've tried twice now to better understand what you're trying to say. In neither case have I been derogatory, mocking, or negative in intent or wording. Yet both times, you seem to have taken offense. You do you, mate, but it is immensely unhelpful to clarifying your point to someone who wanted to understand it.
- hombre_fatal 8y agoSome people just want a leading version number that they can spin manually. For example, the creator of Backbone: https://github.com/jashkenas/backbone/issues/2888#issuecomment-29076249 https://github.com/jashkenas/backbone/issues/2888#issuecomme... I say: why not both.
- hombre_fatal 8y agoI propose RomanticSemVer: {marketing}v{major}.{minor}.{patch}
- paulddraper 8y agohttps://github.com/jashkenas/backbone/issues/2888#issuecomment-29076249 https://github.com/jashkenas/backbone/issues/2888#issuecomme... > So, as I like to joke — not "semantic" versioning, _romantic versioning_. > Given a version number MAJOR.MINOR.PATCH, increment the: > MAJOR version when you make a major new release, or significantly update and/or stabilize the API. > MINOR version when you add minor new features. > PATCH version when you make tiny changes, likely to go unnoticed by most. > This allows folks, immediately upon hearing about a new release, to get a rough sense of its scope.
- hombre_fatal 8y agoHaha, that's exactly who I was thinking of. I linked to it in a sibling comment. I agree with him that having a digit that represents the "era" of the software that can spin on its own is useful. My only problem is that MAJOR is still useful for API changes/breakage, even tiny ones. By adding the ROMANTIC digit, then you, the developer, don't have to be sentimental about MAJOR changes, and your users still know to read the changelog if it changes at all. Because it's definitely true that sometimes MAJOR changes for massive reasons (e.g. 100% rewrite) and sometimes for trivial reasons, and semver doesn't distinguish them. It's hard to answer questions like "so when was the last big change to this library since my version?" just looking at semver major digits. Of course, this is just bike-shedding given how entrenched semver has become, and I certainly prefer semver to what we had before: nothing.
- WorldMaker 8y agoI have projects where I intentionally maintain separate semver and user-facing "romver" (I like that name, I may use it moving forward) version numbers. Semver is at something like 18.x.y and Romver in development is currently at 2.z.w, and may jump "soon" to 6.z.w to match/replace an old VB6 app. For a while with 1.z.w, for simplicity to myself z was the semver MAJOR, but at this point they are almost entirely divorced. ETA: The heavily broadcast user-facing version number of the VB6 app in its usage and marketing being a key reason for needing a "romver" at this point, because users clearly have been trained for decades to expect it.
- _old_dude_ 8y agoI think the main issue is that there is no real semantics when incrementing the major version and no word about deprecation. And BTW, in case of Java since 9, it's the opposite, each new version is a major version.