Skip to content

release/1.9.0: Update .gitmodules for spack: release/1.9.0 --> spack-stack-1.9.1#1567

Merged
climbfuji merged 1 commit intoJCSDA:release/1.9.0from
climbfuji:feature/upd_subm_use_tag_for_spack_191
Mar 14, 2025
Merged

release/1.9.0: Update .gitmodules for spack: release/1.9.0 --> spack-stack-1.9.1#1567
climbfuji merged 1 commit intoJCSDA:release/1.9.0from
climbfuji:feature/upd_subm_use_tag_for_spack_191

Conversation

@climbfuji
Copy link
Copy Markdown
Collaborator

@climbfuji climbfuji commented Mar 14, 2025

Summary

All in the title.

Testing

  • CI RUNNING
  • Verified that the spack submodule hash and code is identical

Applications affected

None

Systems affected

None

Dependencies

None

Issue(s) addressed

Working towards #1485

Checklist

  • This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.

@AlexanderRichert-NOAA
Copy link
Copy Markdown
Collaborator

Would it be better to point to a branch rather than a tag? That way it doesn't have to be retagged for updates.

@climbfuji
Copy link
Copy Markdown
Collaborator Author

Would it be better to point to a branch rather than a tag? That way it doesn't have to be retagged for updates.

We've always done it this way, and it makes it clear that this is the release where tags point to tags and not moving targets.

@climbfuji
Copy link
Copy Markdown
Collaborator Author

Besides, operations at least at NRL requires that.

@climbfuji climbfuji merged commit 6a7e4d2 into JCSDA:release/1.9.0 Mar 14, 2025
9 checks passed
@climbfuji climbfuji deleted the feature/upd_subm_use_tag_for_spack_191 branch March 14, 2025 20:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

No open projects

Development

Successfully merging this pull request may close these issues.

3 participants