Semantic Versioning

Camerata uses semantic versioning, but since this project is mainly about orchestration and doesn't contain much software code itself, follow these guidelines when choosing a version:

1. Major versions (breaking changes) should be incremented when the version requires a cluster rebuild, routing changes, or other changes that are not backward compatible with previous versions
2. Minor versions (features) should be incremented when the version includes new user-facing functionality - in general, the minor version should be incremented if any of the service versions change at the minor version level - i.e. if BLACKLIGHT_VERSION changes from v1.3.4 to v1.4.0, then the Camerata minor release version should increase. The minor version only needs to increase by one regardless of how many component versions change
3. Patch versions (fixes, refactors) should be incremented when there are enhancements or refactors to camerata that do not affect the deployment process (i.e. Documentation remains valid) and/or when updating the patch level of dependent applications