Re:Is Semantic Versioning an Anti-Pattern?
by Sean1708 on Thursday January 12, 2017 @09:36AM
(#13382469)
I'm using feature X. Feature X was introduced in version X.Y. Therefore I can't use any version less than X.Y.
No. When you fix a bug you increment the patch version, unless the fix changes the API in which case you wouldn't want it automatically updated anyway.
[ Parent
| on HN ]
Re:Is Semantic Versioning an Anti-Pattern?
by zilean on Thursday January 12, 2017 @02:21PM
(#13385221)
> I'm using feature X. Feature X was introduced in version X.Y. Therefore I can't use any version less than X.Y.
But it would work the same way with monotonically increasing version. no?
> When you fix a bug you increment the patch version
I am just trying to understand how semver applies to REST in your case. Never seen anything but single number versioning for endpoints.
Re:Is Semantic Versioning an Anti-Pattern?
by Sean1708 on Friday January 13, 2017 @07:53AM
(#13390422)
> But it would work the same way with monotonically increasing version. no?
Kinda. If I can use 1.4 then I can use 1.7 but I can't necessarily use 2.1, because 1.7 only added things to 1.4 but 2.1 changed something about the public interface. > I am just trying to understand how semver applies to REST in your case. Never seen anything but single number versioning for endpoints.
Sorry, I didn't realise we were talking about REST.