As suggested in #1262, it might be useful for there to be a guide for developers on how to make a new release, because there are now a few steps involved.
Off the top of my head, this list should include:
- Checking that the release notes for the "upcoming release" are complete and correct (
docs/release_notes/upcoming.md)
- Rename the file for upcoming release according to the next version, e.g.
docs/release_notes/v2.5.0.md
- Putting a placeholder file for the next upcoming release
- Bumping the crate version in
Cargo.toml
- Bumping the program version specified in
CITATION.cff
There are a few checks related to these in tests/release.rs, but in any case, it would be good to have a set of instructions to help developers along.
As suggested in #1262, it might be useful for there to be a guide for developers on how to make a new release, because there are now a few steps involved.
Off the top of my head, this list should include:
docs/release_notes/upcoming.md)docs/release_notes/v2.5.0.mdCargo.tomlCITATION.cffThere are a few checks related to these in
tests/release.rs, but in any case, it would be good to have a set of instructions to help developers along.