Port ops-hrefv3.1 to WCOSS2

[GeorgeGayno-NOAA]

Port to WCOSS2. Then create a formal release.

Work on this was started under #559. But too many tasks under one issue was getting confusing.

[GeorgeGayno-NOAA]

Working under this branch - 40b8084

[GeorgeGayno-NOAA]

@MatthewPyle-NOAA What machines (other than WCOSS2) must this new release support?

[MatthewPyle-NOAA]

This release is purely for WCOSS2. What is currently in the hrefv3.1-wcoss2 branch in your fork works for me.

[GeorgeGayno-NOAA]

@MatthewPyle-NOAA Sorry I forgot about this. I need to create an official release under the authoritative fork. What did you deliver to NCO?

[MatthewPyle-NOAA]

Looks like I included the branch from your fork:

branch = hrefv3.1-wcoss2
repo_url = https://github.com/GeorgeGayno-NOAA/UFS_UTILS.git

[GeorgeGayno-NOAA]

Looks like I included the branch from your fork:

branch = hrefv3.1-wcoss2 repo_url = https://github.com/GeorgeGayno-NOAA/UFS_UTILS.git

We will need to fix that. I hope it is not too late.

[MatthewPyle-NOAA]

Let me know when you have it where you want NCO to point at it. Probably not that critical as they've already built and run the system, so may never again be pulling it from github, but I'm sure they be okay changing where the externals.cfg points.

[GeorgeGayno-NOAA]

Let me know when you have it where you want NCO to point at it. Probably not that critical as they've already built and run the system, so may never again be pulling it from github, but I'm sure they be okay changing where the externals.cfg points.

@MatthewPyle-NOAA Here is your tag: https://github.com/ufs-community/UFS_UTILS/releases/tag/ops-hrefv3.2

[edwardhartnett]

A formal, versioned release needs to be created.

Is this release a snapshot of the current develop branch?

Or is it a branch of a previous release, which is not the same as the develop branch?