Skip to content

Latest commit

 

History

History
21 lines (17 loc) · 838 Bytes

change-log.md

File metadata and controls

21 lines (17 loc) · 838 Bytes

Developer change log should contain an entry for each release/tag. Each entry should include the new tag version according to SemVer, the date the tag was created, each JIRA issue which work was done against, and a summary of the work completed.

The format for an entry is as follows:

* 1.0.0 (2014-10-30)
  * ABC-123
    * _Major_: description of the major change. Note the upper case letter 'M' in Major
    * _minor_: description of the minor change. Note the lower case letter 'm' in minor
    * _patch_: description of the patch change.

Consult the git commit log for complete details of a release/tag.

Change log (most recent first)

  • 2.2.0 (2017-03-14)
    • minor: Update 'valid-jsdoc' rule from error to warn
  • 2.1.0 (2016-12-06)
    • minor: Enable eslint for VS code's eslint plugin