Skip to content
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

Maintain SERAC_VERSION and create a changelog #1189

Open
chapman39 opened this issue Jul 30, 2024 · 1 comment
Open

Maintain SERAC_VERSION and create a changelog #1189

chapman39 opened this issue Jul 30, 2024 · 1 comment
Assignees
Labels
question Further information is requested user-request Issue requested by user

Comments

@chapman39
Copy link
Contributor

TPL updates for LiDO usually mean sudden breaking changes. There have been some discussions in LiDO about wanting a Serac version to help ease the transition of Serac updates. Though I am not sure how much of a time sink this would become, as Serac is currently still a fast moving target.

Having clear versions would also be nice to do before adding the Serac package to Spack CI #906

@chapman39 chapman39 added question Further information is requested user-request Issue requested by user labels Jul 30, 2024
@chapman39 chapman39 self-assigned this Jul 30, 2024
@chapman39
Copy link
Contributor Author

Since Serac updates often we could adopt a versioning system with YYYY-MM-DD like RAJA: https://github.com/LLNL/RAJA/blob/develop/CMakeLists.txt#L17-L19

Or the more common MAJOR.MINOR.PATCH system like BLT: https://github.com/LLNL/blt/blob/develop/RELEASE-NOTES.md?plain=1#L17

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested user-request Issue requested by user
Projects
None yet
Development

No branches or pull requests

1 participant