forked from pearu/f2py
-
Notifications
You must be signed in to change notification settings - Fork 29
NewRelease
Andy Porter edited this page Dec 15, 2020
·
10 revisions
- Create a "new api x.y.z" issue.
- Make sure you have the latest version of the master branch (clone or checkout master and pull).
- Ensure master is frozen.
- Update the version number in the documentation (
conf.py
). Commit - Update the changelog file (
CHANGELOG.md
). Commit. - Update the 'News' section of the README.md. Commit.
- Update the version number in
setup.py
. Commit - Push changes to origin (
git push
) - Create a new tagged copy using (
git tag -a x.y.z
) where x.y.z is the new version number - Push new tag to origin (
git push --tags
) - Check GitHub has created a new release.
- Push the new release to pypi (see section below)
- Check read-the-docs documentation has updated.
- Check the new pypi release has been created (
sudo pip install fparser --update
) - Close issue
It may be possible to configure a GitHub Action to do this but for now it must be done manually. The steps are:
Make sure you have the latest versions of the necessary packages:
pip install --upgrade setuptools wheel twine
Build the distribution:
cd fparser/
python3 setup.py sdist bdist_wheel
Upload the version you've just built (replace the "0.0.11" below as appropriate). This will prompt for your PyPi credentials:
twine upload dist/fparser-0.0.11*