So I've been researching and looking into versioning my applications correctly rather than coming up with my own scheme. Semantic versioning is a popular option as many of you probably know, but my applications do not really apply to the semantic criteria. By this I mean my product isn't an API. Looking into this, people say semantic versioning is primarily for dependencies.
So my question is, is there a versioning scheme for something like a web application or how can I adapt semantic versioning to suit me.
I came up with the following based of things I could find: So it still uses 0.0.0 = x.y.z
- z: MAJOR: Significant change to UI or code and/or structure
- y: MINOR: New features
- z: PATCH. Bug fixes
This, for the most part, looks like it will work great. Maybe I'm thinking to deeply but when I push a change, not a bug fix or new feature, what is that considered? Patch or minor? I'm just after some advice on how to properly version web applications for an end user, not an API.