-
Notifications
You must be signed in to change notification settings - Fork 394
Release
Benjamin Bossan edited this page Sep 4, 2023
·
14 revisions
- check project board for new release: everything done?
- create a new branch (
release-X.Y.Z
) - change
VERSION
to new version - update
CHANGES.md
- rename
UNRELEASED
section to new version - create new
UNRELEASED
section - update links at the bottom of
CHANGES.md
- rename
- use git grep
TODO
to find and fix deprecations for the new version - commit any changes
- write a nice summary with the highlights of the current release
- push changes
- create PR
- challenge, then merge PR -- add the summary to the commit message
- ensure that current state of master is fetched
- run
PYTORCH_VERSION=1.8.1 ./scripts/deploy.sh stage
(use a recent pytorch version) - verify test results and package on pypi testing
- run
PYTORCH_VERSION=1.8.1 ./scripts/deploy.sh live
(use a recent pytorch version) - verify test results and package on pypi
- create
v<VERSION>
tag using github release tool and add the summary - after the release, update the
VERSION
again, this time to the next higher patch version +dev
(e.g.0.9.0
->0.9.1dev
) - check that a new stable build of the docs was triggered on readthedocs
- release on conda-forge by merging automatically created PR (requires access, so ping BenjaminBossan or, if not available, dhirschfeld)