firesphere

SemVer clearly describes it: >>> Given a version number MAJOR.MINOR.PATCH, increment the:

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.

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

firesphere

Anything "breaking", if the javascript API changes, template syntax changes, PHP API changes, in a way that breaks existing functionality, it's a new major

MichalKleiner

I guess it can be defined, somehow… but I find it hard

MichalKleiner

in the back-end? on the front-end? new SS version? new theme?

nightjarnz

perhaps the difference between "new functionality" vs "changed functionality"?

MichalKleiner

for people using semver to version website releases, how do you define which changes are major or minor?

nightjarnz

a major is better described as "API breaking" - changes are incompatible with the current API.