Skip to content

Maintain wetlands branch on ESCOMP #3906

@ekluzek

Description

@ekluzek

We need to support the wetlands branch (#3893) off of master, for a month or so, before it can merge to master. It needs to stay off of master since it changes answers for the coupled model, and we can't bring it in until the offline spinup step. That step is expected to be completed mid Summer. But, we might be able to assess and bring it into master sometime before that maybe a month or so.

The steps to do:

  • Create the wetlands branch rules in github from Settings / Branches / Add rule (same rules as b4b-dev)
  • Create the wetlands branch in github from Code / Branches / New branch (or in the command line)
  • Rebase branch_tags/wetlands.n01.ctsm5.4.029: Wetland update #3893 to merge onto the wetlands branch
  • Tag first wetlands annotated branch tag: branch_tags/wetlands.n01.ctsm5.4.029 (process same as for master but without updates to ChangeLog)

Things that will be done on an ongoing basis as needed:

  • Update branch to latest master and test/tag it (just before a simulation is done)
  • Run simulations with tags along the branch

When merged to master:

  • Use PR's along the branch to make the ChangeLog
  • Can delete the branch and branch rules after it's merged to master

Metadata

Metadata

Labels

devopsDevelopment Operations to improve development throughput, E.g., adding GitHub Workflowsenhancementnew capability or improved behavior of existing capabilitynon-bfbChanges answers (incl. adding tests)scienceEnhancement to or bug impacting science

Type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions