1 The first line should be a single-line "purpose" for this change
3 TYPE: choose one of [bug fix, enhancement, new feature, feature removed, no impact, text only]
5 KEYWORDS: 5 to 10 words related to commit, separated by commas
7 SOURCE: Either "developer's name (affiliation)" .XOR. "internal" for a WRF Dev committee member
9 DESCRIPTION OF CHANGES:
11 Generally or specifically, what was wrong and needed to be addressed?
14 What was down algorithmically and in the source code to address the problem?
16 ISSUE: For use when this PR closes an issue.
19 LIST OF MODIFIED FILES: list of changed files (use `git diff --name-status master` to get formatted list)
22 1. Do mods fix problem? How can that be demonstrated, and was that test conducted?
23 2. Are the Jenkins tests all passing?
25 RELEASE NOTE: Include a stand-alone message suitable for the inclusion in the minor and annual releases. A publication citation is appropriate.