-
Notifications
You must be signed in to change notification settings - Fork 25
Home
P. L. Lim edited this page Jul 31, 2020
·
15 revisions
- GitHub
- PyPI (bot picks up from GitHub release)
- astroconda
- conda-forge (bot picks up from PyPI)
- Zenodo
There are some old release branches but this package is low-traffic enough that we stopped using release branches.
- 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) andgit log
(must contain correct history) - Finalize release date on change log, add, and commit it.
git clean -xdf
-
git tag -s "X.Y.Z" -m "Tagging version X.Y.Z"
(replaceX.Y.Z
with real version number) -
git push <remote> X.Y.Z
(replace<remote>
with remote name that points to this repo) - Add new change log entry for next release, add, and commit it.
git push <remote> master
git checkout stable
git reset --hard <version>
git push <remote> stable --force
- Edit release tag on GitHub to add change log and publish release.
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/synphot/ .
- Open a PR on
astroconda/astroconda-contrib
to update recipe. Usually this is done together withstsynphot
. - 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/synphot/builds/