Develop

Overview

Modify the codebase to add a new feature, fix a bug or make an improvement.

Process

A Jira issue should be created before any Development takes place, capturing the feature specification or bug report. This ensures that requirements are captured in a single place, stores conversation around the development, and tracks progress and workflow towards release.

Every feature/bugfix should be developed on a separate Git branch (feature branch) named with the JiraID (eg feature/METL-123). This ensures that releases can be assembled from individual items, and that if an item is no longer required, or fails testing, the release can be recreated from the original items without the undesirable item.

Every commit message should start with a JiraID (eg METL-123). This ensures that when feature branches are deleted (after release to production) the Git history is an accurate reflection of why a code change was made, and can be linked back to the original specification.

Grunt

Grunt is run via grunt.sh. Before this will work, grunt needs to be installed via npm:

> cd src/main/assets/build
> npm install