About Versions in the Journey Platform

   Journey PlatformPreviously known as the Transact Platform.  |   All Personas |  5.1 & Higher This feature is related to 5.1 and higher.

The Temenos Journey Platform contains assets and resources that usually need to be managed across several versions; for example, to maintain backwards compatibility, or to control the release of new features. A common approach to version management, based on semantic versioning, is recommended for use with all Journey products.

Semantic versioning uses version numbers in the format MAJOR.MINOR.PATCH. A version number may be extended with an optional label suffix that usually denotes a pre-release version such as alpha, beta or develop. So, a version number might look like 2.0.5 or 1.0-develop.

There are many approaches or strategies for applying versions, and you should choose one that is appropriate for your circumstances. Semantic versioning is a recommended approach for managing the assets and resources created by or for use with Journey products. If you decide to use this approach, you should follow the semantic versioning guidance more closely:

  • Increment MAJOR when you make incompatible changes or add significant new functionality
  • Increment MINOR when you add functionality in a backwards-compatible manner
  • Increment PATCH when you make backwards-compatible bug fixes
  • Use additional labels as extensions to the MAJOR.MINOR.PATCH format

Next, learn about releases.