Home

Where to release

• GitHub
• PyPI (bot picks up from GitHub release)
• conda-forge (bot picks up from PyPI)
• astroconda
• Zenodo

How to release on GitHub

1. Grab latest code from master
2. Grab all the tags from this repo
3. Make sure you are on the branch that you intend to release from
4. Check git status (must be clean) and git log (must contain correct history)
5. git clean -xdf
6. git tag -s "X.Y.Z" -m "Tagging version X.Y.Z" (replace X.Y.Z with real version number)
7. git push <remote> X.Y.Z (replace <remote> with remote name that points to this repo)
8. Edit release tag on GitHub to add change log and publish release.

How to release on PyPI

Check the logs under Actions. This should be done automatically when a GitHub Release is made. If successful, you will see it on https://pypi.org/project/acstools/ .

Other release outlets

• Open a PR on astroconda/astroconda-contrib to update recipe.
• Wait for a notification from conda-forge feedstock, review its PR, fix (if needed), and merge.
• Download the release tarball from PyPI and upload it to Zenodo.
• Check https://readthedocs.org/projects/acstools/builds/

Lack of milestone

This is a low-traffic package. Therefore, there is no milestone being used to track GitHub PRs. A release is made when ACS Team wants it and whether it is a major/minor/bugfix depends on what went in since the last release.