Skip to content

Latest commit

 

History

History
16 lines (14 loc) · 1019 Bytes

how-to-release-a-new-version.md

File metadata and controls

16 lines (14 loc) · 1019 Bytes

How to release a new version?

Releasing a new version helps to bring out new features and improvements to our customers. To keep track of all changes we do the following:

  1. update the POM file with the new version number (using Calendar Versioning style YY.0M.MICRO since 20.05)
  2. add the new version, a release title and the release date to the Changelog
  3. update the Compatibility Matrix with the new version number
  4. create a tag for the new version with reference to the latest commit 
    git rev-parse HEAD
git tag -a <version> -m "<version>" <commit hash>
git push origin <version>
  5. upload and promote the new version at Atlassian Marketplace
  6. add new version number to Service Desk versions