Under Consideration

Semantic versioning for Process and Forms

This is a request to enable semantic versioning for both Process and Forms in Bizagi. As per http://semver.org/

Given a version number MAJOR.MINOR.PATCH, increment the:

  • MAJOR version when you make incompatible API changes,
  • MINOR version when you add functionality in a backwards-compatible manner, and
  • PATCH version when you make backwards-compatible bug fixes.
  • At the moment of writing Bizagi supports only [major].[minor] versioning. As a result you can not tell by versioning number whether a Process in Development or Production are on the same patch level . On the contrary, it is possible to have in Development and Production the same process with version 1.0 while they differ in Entities attributes and/or Form elements. If the team rolls out regular updates on existing processes this can become very confusing.

    It would be really helpful if it was possible to specify the patch level before actually executing a deployment or even when starting working on it. Hence, at any point you can view the exact versioning number in both Production i.e. 1.0.1 and Development i.e. 1.0.2 env. This will be also helpful for planning releases ahead.

    Thank you.