Skip to content

Added release naming convention explanation #1063

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.

Sign up for GitHub

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

Merged
stelliom merged 1 commit into from
Dec 17, 2025
Merged

Added release naming convention explanation #1063

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -64,6 +64,16 @@ rm -rf ~/.spack
```
After an update we advice to rebuild packages, preferably in a new shell so that no outdated shell variables are retained.

## Releases/Tags

When creating a new release tag please follow the naming convention below:

```
v${SPACK_VERSION}.${SPACK_C2SM_VERSION}
```

Where `SPACK_VERSION` corresponds to the upstream Spack version this repo is based on, e.g. `SPACK_VERSION=0.22.2`. `SPACK_C2SM_VERSION` is the number of releases based on a specific `SPACK_VERSION`, starting from 0, which corresponds to the release adapting spack-c2sm to a new upstream Spack version. So, for example v0.22.2.5 is the fifth (sixth if you count the transitional release v0.22.2.0) spack-c2sm release based on Spack v0.22.2.

## Command cheat sheet
| | Command |
| --- | --- |
Expand Down