-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
spack-stack-1.9.0 release tasks #1485
Comments
Interesting thought here for Discover. I'm going to consult @Dooruk, but I'm thinking we might not need to have both SLES12 (SCU16) and SLES15 (SCU17) stacks. NCCS is very close to finally killing off SLES12 on the system. The Skylakes are gone and the number of Cascade Lake nodes on SLES12 is trending towards zero. Frankly, NCCS would probably prefer no one even run on SLES12 if possible anymore. |
Yeah, we won't need/use SLES12 modules in our workflow anymore. One less thing to worry about! |
On Acorn, I'm getting duplicates of esmf on account of the 'preferred: +python' in the common settings. I can make it go away by setting a require one way or the other. Can we do a require one way or the other, then override for individual sites if needed? |
@AlexanderRichert-NOAA ot seeing that behavior, but would agree with your proposal. |
Since folks started installing, would it be possible to overwrite the preferred with a require for Acorn, and fix it as you suggested on develop? |
hera / hercules / orion / ursa are complete (and will be re-built when the |
List of tasks for the release
Project board: https://github.com/orgs/JCSDA/projects/9/views/1
doc/source/conf.py
and.gitmodules
to userelease/1.9.0
instead ofdevelop
blueback(@climbfuji; not yet available)navy-aws(@climbfuji; not yet available)JCSDA AWS Parallelcluster[no release unless requested]doc/source/conf.py
and.gitmodules
to use tag instead of release branch, tag spack-stack (@climbfuji)The text was updated successfully, but these errors were encountered: