3 ms·
Why not encode further information into the number, if that's what you want? 1004.0.0 to 1005.0.0 is an api-major business-minor version bump (incompatible API
by remram 3y ago
Why not encode further information into the number, if that's what you want?
1004.0.0 to 1005.0.0 is an api-major business-minor version bump (incompatible API). Semver-compatible.
1004.0.0 to 2000.0.0 is an api-major business-major version bump. There, the first number has changed, if that's important to you. Semver-compatible.
1004.0.0 to 1004.1.0 can be the "INCREMENT" thing they also mention.
As a bonus, your version number is soon going to be much higher than competitors. That's sure to impress clients. You can refer to the 9000-line easy enough.
- cush 3y agoNeeds more bitmasking
- remram 3y agoOnly if a machine wants to read the business number, which it doesn't.
- colejohnson66 3y agoWhy not just have a four part version number? * 1.4.0.0 to 1.5.0.0 * 1.4.0.0 to 2.0.0.0 * 1.4.0.0 to 1.4.1.0
- remram 3y agoNot semver-compatible.
- yencabulator 3y agoNeither are breaking changes in a minor-according-to-semver bump.
- remram 3y agoMy point is that you don't have to do that. You still do a major version bump for breaking changes, you just have another number before that, for your business communication concerns.