Prepare for Release

Overview

Creating a release from one-to-many issues and versioning it in the form: [major].[minor].[build] (guided by Semantic Versioning).

Process

Git: Merge required feature branches into release branch.

Jira: Transition issues to Merged to /release.

Determine version number of release (whether to increment a major, minor or build number).

Jira: Set fix version on each issue to new version number.

Git: Checkout the release branch.

Generate .css files from .less, and run other grunt tasks:

$ sh ./grunt.sh

Minify .js files:

$ sh ./minify.sh

Update the build number in both src/main/resources/version and build.sbt.

Update src/main/resources/release-notes to contain the new version and a summary of the issues in the release.

Ensure that html files are importing minified javascript (should be <script src="static/js/min/conversationSearch.js"></script> not <script src="static/js/conversationSearch.js"></script>).

Check:

• admin.html
• board.html
• clientSidePrintConversation.html
• conversations.html
• conversationSearch.html
• dashboard.html
• editConversation.html
• enterprise.html
• mobile.html
• remotePluginConversationChooser.html

Git: Commit.

Git: Tag with the version number. It is bad practice to move an existing tag. If a version needs rebuilding, increment the build component of the version instead.