Home

Where to release

There are some old release branches but this package is low-traffic enough that we stopped using release branches.

pip install pep517 --upgrade
Grab latest code from master
Grab all the tags from this repo
Make sure you are on the branch that you intend to release from
Check git status (must be clean) and git log (must contain correct history)
git clean -xdf
Finalize change log for release, add, and commit.
git tag -s "X.Y.Z" -m "Tagging version X.Y.Z" (replace X.Y.Z with real version number)
git checkout X.Y.Z
umask 0022
chmod -R a+Xr .
python -m pep517.build --source .
git push <remote> X.Y.Z (replace <remote> with remote name that points to this repo)
gpg --detach-sign -a dist/*.tar.gz (requires GPG to be set up)
twine check dist/*
twine upload dist/*.tar.gz* (requires write access to PyPI package area)
git checkout master
Add change log entry for next release, add, and commit.
git push origin master
git checkout stable
git reset --hard <version>
git push <remote> stable --force
Edit release tag on GitHub to add change log
Upload dist/*.tar.gz to Zenodo (requires write access to Zenodo page)

Open a PR on astroconda/astroconda-contrib to update recipe. Usually this is done together with stsynphot.
Wait for a notification from conda-forge feedstock, review its PR, fix (if needed), and merge.
Check https://readthedocs.org/projects/synphot/builds/