Release Process

Release Process

These notes enumerate the steps required every time we release a new version of Arbor.

Pre-release: update tags/versions and test

See https://docs.arbor-sim.org/en/latest/contrib/release.html

Pre-release: manually test

See https://docs.arbor-sim.org/en/latest/contrib/release.html

Pre-release: ciwheel/automated test

See https://docs.arbor-sim.org/en/latest/contrib/release.html

Release

See https://docs.arbor-sim.org/en/latest/contrib/release.html

Post release

1. See https://docs.arbor-sim.org/en/latest/contrib/release.html
2. In the same PR with the update to spack/package.py, might as well bump VERSION file.
3. Announce on our website
4. Add release for citation on Zenodo, add new ID to docs
5. Add tagged version of docs on ReadTheDocs (should happen automatically)
6. HBP internal admin

• Plus
• TC Wiki
• KG - Update howto.
  • Supported file formats (ie ContentTypes), details
• Send an update to the folk in charge of HBP Twitter if we want to shout about it

7. FZJ admin

• https://juser.fz-juelich.de/submit