-
Notifications
You must be signed in to change notification settings - Fork 56
Release
Core developers should follow this procedure when making a new release of pyGSTi:
-
Merge
beta
intomaster
.Merge the content of the release into
master
. There may be hotfixes or other small patches inmaster
which aren't inbeta
ordevelop
-- keep needed hotfixes, and remove unneeded ones. -
Make sure this version of
master
is what you want to release.You can use
git diff origin/master
to compare your branch with the last release. -
Create a new tag with the incremented version number for the release.
Use
git tag -a $VERSION -m "PyGSTi version $VERSION"
, where$VERSION
is the incremented version number, likev0.9.7.5
. -
Push
master
and the new tag to the remote repository.Use
git push --tags origin master
. Only core pyGSTi developers can push tomaster
-- you'll be informed if you don't have sufficient permissions. If you get aremote: Internal Server Error
message you might need to increase the max POST buffer size using a command likegit config --global http.postBuffer 157286400
. Also, pushing to master can be done more explicitly in two steps bygit push
(to push the master branch) andgit push origin "v$VERSION"
(to push the tag). -
Watch the CI build. Make sure it passes and deploys the new version to PyPI. When the CI builds the tag, the final "deploy" stage should automatically send the new version to PyPi.