-
Notifications
You must be signed in to change notification settings - Fork 312
Minor Version Update Protocols
Minor version updates are when the second number in the tag changes (i.e. ctsm6.0.176 to ctsm6.1.0). Major version updates are when the first number changes (i.e. ctsm6.5.176 to ctsm7.0.0). Major version updates follow this as well and just add additional requirements.
-
Run the following tests: namelist, python, aux_clm, ctsm_sci, fates, mosart, rtm, tools
-
ctsm_sci baselines have a ctsm_sci- prefix to the tag name
-
FATES baselines have the normal fates- prefix with the FATES version and then the CTSM version
-
mosart baselines have the mosart version as a prefix
-
rtm baselines have the rtm version as a prefix
-
Simulations should be performed and verified at least working up to the final version (normally spinup and transient for standard resolution)
-
Compare namelists between the previous tag and what will become the new minor version update
cd $SCRATCH
git clone --origin escomp -b <previous_tag> <giturl>/ESCOMP/CTSM.git <previous_tag>
cd bld/unit_testers`
./build-namelist_test.pl --generate
cd <location_of_clone_for_new_tag>
cd bld/unit_testers
./build-namelist_test.pl --generate
./compare_namelists --physicsA <old_physics_version> --physicsB <new_physics_version>
- Similarly compare namelists between the previous tag that had ctsm_sci testing on it and what will become the new minor version update
- Similarly compare namelists between the previous minor version tag and what will become the new minor version update
Make sure that the changes appear as expected.
Compare the ctsm_sci tests by making sure all the new tests are run in the older version (with the previous physics version) Create softlinks to the new version in the previous ctsm_sci test baseline that have the new version in it Compare the new namelists to the older one to make sure the changes are as expected
cd bld/unit_testers
./build-namelist_test.pl
./compare_namelists --physicsA <old_physics_version> --physicsB <new_physics_version>
- Review the final version before it comes in as a tag.
- Review the README files to make sure they are still accurate
- Simulations are required to go along with a major version update
- User's Guide and Technical note need to be updated
-
General
-
Documents
-
Bugs/Issues
-
Tutorials
-
Development guides
CTSM Users:
CTSM Developer Team
-
Meetings
-
Notes
-
Editing documentation (tech note, user's guide)