Skip to content

Versioning

Jump to bottom
mdemeyer edited this page Sep 21, 2020 · 1 revision

Semver

Both the octa-stack itself and the applications have versioning. Semantic versioning is used, with the basic idea of:

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.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

The current application version number is set in the Makefile of the application for the application, and the Makefile.core for the octa-stack.

On top of the version number itself, a changelog.txt file is kept for each application and the stack. This file has to be updated each time a new version is added.

Git Tagging

Furthermore, git commits for a new version should be tagged with a version number once this version changes from the previous one, , making a checkout of previous versions easier.
For a new application version, it should be: applicationname-v0.1.2.
For a new stack version, it should be: v0.1.2.

Clone this wiki locally