-
Notifications
You must be signed in to change notification settings - Fork 353
Maintain wetlands branch on ESCOMP #3906
Copy link
Copy link
Open
Labels
devopsDevelopment Operations to improve development throughput, E.g., adding GitHub WorkflowsDevelopment Operations to improve development throughput, E.g., adding GitHub Workflowsenhancementnew capability or improved behavior of existing capabilitynew capability or improved behavior of existing capabilitynon-bfbChanges answers (incl. adding tests)Changes answers (incl. adding tests)scienceEnhancement to or bug impacting scienceEnhancement to or bug impacting science
Metadata
Metadata
Assignees
Labels
devopsDevelopment Operations to improve development throughput, E.g., adding GitHub WorkflowsDevelopment Operations to improve development throughput, E.g., adding GitHub Workflowsenhancementnew capability or improved behavior of existing capabilitynew capability or improved behavior of existing capabilitynon-bfbChanges answers (incl. adding tests)Changes answers (incl. adding tests)scienceEnhancement to or bug impacting scienceEnhancement to or bug impacting science
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:
Things that will be done on an ongoing basis as needed:
When merged to master: