Version Management
How does version management work in Mantsu?
Audience: This page is intended for project stakeholders and application owners. It explains in plain terms how template versions and your project-specific customizations are kept under control.
Version management in Mantsu keeps both the delivered templates and your project specific customizations under control, each with its own versioning. It 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.
How are template versions managed?
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.
How are project customizations versioned?
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.
Summary: Mantsu separates template versions, maintained by Mayker, from project customization versions owned by you. Every application is versioned separately, so you can upgrade and customize per module.