Version Management

version management is split into 2 types depending on the use of mantsu template version management project customization version management template versions are maintained by mayker and follow an internal versioning when a project is started from a template; the version of the templates is copied into the project specific version and a customization version is added instead of the built version versions are created for each application in mantsu separately there is no general version template version management the internal template uses semantic versioning with three components major minor build major increments on breaking changes (schema migrations, core redesign, non backward compatible refactoring) minor increments on non breaking feature additions (new optional fields, new modules, backward compatible enhancements) build auto incrementing counter for each successful development iteration, used for bug fixes project customization version management each customer project receives a version number derived from the template version active at project creation time major minor update major minor copied from the template version at the moment the customer project was initialized these remain fixed for the project's lifetime to maintain traceability update a sequential number (1, 2, 3, …) that increments each time the customer project is deployed or updated resets to 1 if the template is upgraded (forcing a major or minor version bump) when a project customization is upgraded to a new version of the template a technical expert will review the impact and will provide an assessment of the required effort each customization has impact on the upgrade effort // visueel toevoegen > branching strategie etc