Creating a release

Version schema:

• General: major.minor.patch (semver)
• Pre-releases (release candidates) must end with ~XX where XX is the number of the pre-release
  • So, before version 7.1.1 is released, there may be versions 7.1.1~01, 7.1.1~02, and so on
• Releases don't have a suffix.
  • So, once version 7.1.1 is ready, it is published as 7.1.1
• This concept ensures that stable releases are always evaluated as a higher version number than pre-releases.

The following steps have to be followed to create a release:

1. Update the changelog file
2. commit all changes
3. Do a git push: git push
4. Create a git tag in the format v+VERSION (eg. v7.0.0): git tag vVERSION
5. Push tags: git push --tags

In case of a mistake, the tag can be deleted:

1. Locally: git tag -d vVERSION
2. Remotely: git push --delete origin vVERSION