forked from ESCOMP/CTSM
-
Notifications
You must be signed in to change notification settings - Fork 0
/
.ChangeLog_template
123 lines (74 loc) · 3.2 KB
/
.ChangeLog_template
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
===============================================================
Tag name:
Originator(s):
Date:
One-line Summary:
Purpose of changes
------------------
[Fill this in with details]
Bugs fixed or introduced
------------------------
Issues fixed (include CCTSM Issue #): [If none, remove this line]
CIME Issues fixed (include issue #): [If none, remove this line]
Known bugs introduced in this tag (include github issue ID): [If none, remove this line]
Notes of particular relevance for users
---------------------------------------
Caveats for users (e.g., need to interpolate initial conditions):
Changes to CLM's user interface (e.g., new/renamed XML or namelist variables):
Changes made to namelist defaults (e.g., changed parameter values):
Changes to the datasets (e.g., parameter, surface or initial files):
Substantial timing or memory changes:
Notes of particular relevance for developers: (including Code reviews and testing)
---------------------------------------------
Caveats for developers (e.g., code that is duplicated that requires double maintenance):
Changes to tests or testing:
Code reviewed by:
Did you follow the steps in .CLMTrunkChecklist:
CLM testing:
[... Remove before making trunk_tag. Available test levels:
a) regular (must be run before handing off a tag to SEs and must be run
before committing a tag)
b) build_namelist (if namelists and/or build_system changed))
c) tools (only if tools are modified and no CLM source is modified)
d) short (for use during development and in rare cases where only a small
change with known behavior is added ... eg. a minor bug fix)
e) doc (no source testing required)
... ]
[PASS means all tests PASS and OK means tests PASS other than expected fails.]
build-namelist tests:
cheyenne -
unit-tests (components/clm/src):
cheyenne -
tools-tests (components/clm/test/tools):
cheyenne -
PTCLM testing (components/clm/tools/shared/PTCLM/test):
cheyenne -
regular tests (aux_clm):
cheyenne_intel ----
cheyenne_gnu ------
hobart_nag --------
hobart_pgi --------
hobart_intel ------
CLM tag used for the baseline comparisons:
Answer changes
--------------
Changes answers relative to baseline:
If a tag changes answers relative to baseline comparison the
following should be filled in (otherwise remove this section):
Summarize any changes to answers, i.e.,
- what code configurations:
- what platforms/compilers:
- nature of change (roundoff; larger than roundoff/same climate; new climate):
If bitwise differences were observed, how did you show they were no worse
than roundoff?
If this tag changes climate describe the run(s) done to evaluate the new
climate (put details of the simulations in the experiment database)
- casename:
URL for LMWG diagnostics output used to validate new climate:
Detailed list of changes
------------------------
List any svn externals directories updated (cime, rtm, mosart, cism, etc.):
List all files eliminated:
List all files added and what they do:
List all existing files that have been modified, and describe the changes:
===============================================================