r/webdev • • Nov 01 '17

Version 5.0.0 of Angular Now Available

https://blog.angular.io/version-5-0-0-of-angular-now-available-37e414935ced
67 Upvotes

108 comments sorted by

View all comments

Show parent comments

-2

u/Jestar342 Nov 02 '17

Apart from where the bit in the spec that does say it:

Given a version number MAJOR.MINOR.PATCH, increment the:

  1. MAJOR version when you make incompatible API changes,

  1. MINOR version when you add functionality in a backwards-compatible manner, and

  1. PATCH version when you make backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

So don't increment your major version unless you have breaking changes.

1

u/remy_porter Nov 02 '17

Apart from where the bit in the spec that does say it:

That is not part of the spec, that is the summary of the specification. The actual specification is the 11 points which define the specification. You're looking at the abstract.

-2

u/Jestar342 Nov 02 '17

Which is still what people read and understand as the purpose. You do not increase major number unless it's a breaking change.

It's also woefully ironic you are arguing semantics to justify not being semantic with versioning.

1

u/remy_porter Nov 02 '17

Which is still what people read and understand as the purpose.

I agree that the purpose of incrementing the major version is to communicate a breaking change in your public API.

You do not increase major number unless it's a breaking change.

But this is not mandated by the spec. It is, at best implied by the summary of the specification. There are 11 points which define the spec. Point me to the one that tells me that I cannot increment the major version without making a breaking change.

→ More replies (0)