-
Notifications
You must be signed in to change notification settings - Fork 1
versioning
Jonathan Smith edited this page May 23, 2018
·
2 revisions
Looking at https://semver.org/spec/v2.0.0.html#summary
- MAJOR version when you make incompatible API changes
- MINOR version when you add functionality in a backwards-compatible manner, and
- PATCH version when you make backwards-compatible bug fixes.
Breaking/major:
- If we imagine our application as a library that takes
dataandconfigas parameters, we can think of a MAJOR (breaking) change as one where the same data and config would break the application. - We might also want to change the major version when we make substantial changes to the UI