forked from wrf-model/WRF
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge remote-tracking branch 'origin/release-v4.2.1'
- Loading branch information
Showing
34 changed files
with
344 additions
and
190 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,32 @@ | ||
--- | ||
name: Bug report | ||
about: 'Issues are typically for demonstrable errors in the software. User problems | ||
with a build should be directed to the WRF Forum: forum.mmm.ucar.edu' | ||
title: '' | ||
labels: '' | ||
assignees: davegill | ||
|
||
--- | ||
|
||
**Describe the bug** | ||
A clear and concise description of what the bug is. | ||
|
||
**To Reproduce** | ||
Steps to reproduce the behavior: | ||
1. Use compiler and version '....' | ||
2. Use namelist options '....' | ||
3. Output is '....' | ||
|
||
**Expected behavior** | ||
A clear and concise description of what you expected to happen. | ||
|
||
**Screenshots** | ||
If applicable, add screenshots to help explain your problem. | ||
|
||
**Attachments** | ||
If applicable, attach supporting files: namelist.input, rsl.* files, etc. | ||
|
||
**Additional context** | ||
Add any other context about the problem here, such as: | ||
- This used to work with a previous version. | ||
- The documentation is different from the exhibited behavior. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,23 +1,25 @@ | ||
Use this template to give a detailed message describing the change you want to make to the code. | ||
If you are unclear on what should be written here, see https://github.com/wrf-model/WRF/wiki/Making-a-good-pull-request-message for more guidance | ||
|
||
The title of this pull request should be a brief "purpose" for this change. | ||
|
||
--- Delete this line and those above before hitting "Create pull request" --- | ||
The first line should be a single-line "purpose" for this change | ||
|
||
TYPE: choose one of [bug fix, enhancement, new feature, feature removed, no impact, text only] | ||
|
||
KEYWORDS: approximately 3 to 6 words (more is always better) related to your commit, separated by commas | ||
KEYWORDS: 5 to 10 words related to commit, separated by commas | ||
|
||
SOURCE: Either "developer's name (affiliation)" .XOR. "internal" for a WRF Dev committee member | ||
|
||
DESCRIPTION OF CHANGES: One or more paragraphs describing problem, solution, and required changes. | ||
DESCRIPTION OF CHANGES: | ||
Problem: | ||
Generally or specifically, what was wrong and needed to be addressed? | ||
|
||
Solution: | ||
What was down algorithmically and in the source code to address the problem? | ||
|
||
ISSUE: For use when this PR closes an issue. For example, if this PR closes issue number 123 | ||
ISSUE: For use when this PR closes an issue. | ||
Fixes #123 | ||
|
||
LIST OF MODIFIED FILES: list of changed files (use `git diff --name-status master` to get formatted list) | ||
|
||
TESTS CONDUCTED: Explicitly state if a WTF and or other tests were run, or are pending. For more complicated changes please be explicit! | ||
TESTS CONDUCTED: | ||
1. Do mods fix problem? How can that be demonstrated, and was that test conducted? | ||
2. Are the Jenkins tests all passing? | ||
|
||
RELEASE NOTE: Include a stand-alone message suitable for the inclusion in the minor and annual releases. A publication citation is appropriate. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,4 +1,4 @@ | ||
WRF Model Version 4.2 | ||
WRF Model Version 4.2.1 | ||
|
||
http://www2.mmm.ucar.edu/wrf/users/ | ||
|
||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.