@WeiWei-NCO please take a look if you get a chance. This should encapsulate everything I've already incorporated into release/1.6.0-nco, idea being that in the future, starting with 1.9.0, we shouldn't need a separate NCO branch.

Nothing jumps out at me.

starting with 1.9.0, we shouldn't need a separate NCO branch.

As long as each code delivery from EMC has a new version number, and only the related files get updated. We don't expect many spack-stack changes or package.yaml changes in the spack sub when the delivery is only to upgrade certain library/libraries.

@AlexanderRichert-NOAA I changed the base branch to release/1.9.0 (let's merge site config updates directory into the release branch, then bring everything back to develop once the release is tagged). Can you please merge this when you think it is ready (maybe ping @Hang-Lei-NOAA to review and approve)?

Sounds good, will do, thanks.

I need to revert one module-related change then this is ready to go.

@Hang-Lei-NOAA @edwardhartnett please review & approve

@climbfuji would you be averse to me force-merging this since it's all wcoss2 site and nco template changes?

Go ahead please, the GNU failure needs cherry-picking a commit from develop