In order to build ACCESS-ESM1.6 with OASIS3-MCT v5.0 this version of the code needs to be added to this repo from the upstream GitLab repo.
The older code in this repo was added as a single commit that corresponds to the upstream code at commit 01ef8708c.
Options to manage this:
- Create a
v5 branch and add the upstream code (with no shared history to main)
- Move current
main to v3 and push the current upstream/OASIS-MCT_5.0 to main (or v5 and make default)
- Move current
main to v3 and push the current upstream/OASIS-MCT_6.0 to main (or v6 and make default)
- ???
Option 1 is the simplest.
Option 2 is a bit more consistent and allows for some additions to the branch, e.g. CI and #39.
Option 3 might be favoured if we think OASIS v6 is required in the future, as we'll pick out tags for the v5 code we want to build with.
Do we need CI if we're not changing this code much (at all?).
Opinions welcome @dougiesquire @manodeep @anton-seaice @penguian
In order to build ACCESS-ESM1.6 with OASIS3-MCT v5.0 this version of the code needs to be added to this repo from the upstream GitLab repo.
The older code in this repo was added as a single commit that corresponds to the upstream code at commit
01ef8708c.Options to manage this:
v5branch and add the upstream code (with no shared history tomain)maintov3and push the currentupstream/OASIS-MCT_5.0tomain(orv5and make default)maintov3and push the currentupstream/OASIS-MCT_6.0tomain(orv6and make default)Option 1 is the simplest.
Option 2 is a bit more consistent and allows for some additions to the branch, e.g. CI and #39.
Option 3 might be favoured if we think OASIS v6 is required in the future, as we'll pick out tags for the v5 code we want to build with.
Do we need CI if we're not changing this code much (at all?).
Opinions welcome @dougiesquire @manodeep @anton-seaice @penguian