Elastic Path Commerce Development

Version Number Conventions

Version Number Conventions

The following conventions are recommended for versioning customer projects:

Best practices

Do not reversion development branch on each release

  • Updating the development branch version number on each release is additional work, adds noise to the commit history, and provides marginal value.
  • It is more effective to update version number only on release branches and to use the same development version throughout the project.

Update versions numbers only on the release branch

  • Update versions numbers on the release branch immediately after it is created. This will distinguish release artifacts from development artifacts.
  • Do not merge version number changes back into development.