We’ll strive to use Semantic Versionin https://semver.org/
...
We added a new feature that needs some DB changes not breaking anything → MINOR, PATCH
We modified a feature to make more easy for the end user → MINOR, PATCH
We added a new feature that breakes the DB → x - NO WAY
We have always to care about previous version by providing migration scripts
When we change MAJOR?
Altough we strive to keep each version fully compliant with the previous ones (just adding new features, and we provide migration script between versions) “lifes goes on and… libraries change!” so it would be possible that some dependencies stop being available and brake breaks some features, in that case we’ll have a MAJOR bump IF we cannot workaround the problem.
We are planning to release soon OpenHospital 2.0 (WIP) (core + api + ui) for which will be very hard (let’s say impossible) to make it working with the same identical libraries, hence the MAJOR version bump.
...