- Update RELEASE.md - It should be in based on milestone description.
- Commit the changes:
git add RELEASE.md
git commit -m "Changelog for upcoming release <version>"- Final check
READMEandCONTRIBUTING.
- Update version number (can also be minor or major)
- Check if we need to upgrade
REQUIRES_PYTHONorREQUIREDdependencies.
- Check if we need to upgrade
- Update
download_urlin setup - Check if local installation can be done.
- Run the tests
- Run the formatting
- CI Check
python -m pytest
make all
- Update version label on documentation
- docs/conf.py
- docs/documentation.rst
- Update Sphinx
- Update version label on website
- BEYOND THIS, EACH STEP SHOULD BE DONE IN SERIAL (STEP_BY_STEPS). -- Rebase the commit history (should be done by only one person) right before the PR.
- Submit a pull request to private. Have it reviewed and merge.
- Push the merged branch (master/main) into the public repo.
- Mark the tag in a public repo.
git push --tags - Release on PyPI by uploading both sdist and wheel:
python setup.py sdist upload
python setup.py bdist_wheel upload
- Test that it pip installs
- Check the PyPI listing page to make sure that the README, release notes, and roadmap display properly.
- Edit the release-page on GitHub. Paste the release notes with a title for the release.