-
Notifications
You must be signed in to change notification settings - Fork 56
Home
-
Create a release branch (on GitHub) for each new major or minor release, i.e.
3.1_relonto which all the 3.1.x releases will live. -
Clone repo and checkout release branch, unless otherwise noted all the rest of these commands will be on that branch.
-
In
setup.pychangedefault_versionto be the tag of the release you are creating. i.e.3.1.0 -
Similarly in
docs/sources/conf.pychangesversionandreleaseto the same tag. -
Check in in those changes above.
-
Create the git tag for that release:
git tag 3.1.0.
At this point a git describe --tags --dirty should show the release tag (3.1.0) and nothing else (not 3.1.0rc0-dirty, etc.) Build, test, take notes on new issues to file...
-
push the changes but not the tag up to github:
git push -
Create the release using the web interface (make sure to create the release/tag on the release branch).
-
Update readthedocs so that it builds from the new tag and uses that as the default version to display.
-
Announce the release.