The gwf build, testing and deployment process is automated through Travis.
Make sure that the changes have proper test coverage, e.g. by checking the branch on Coveralls.
Check that the PR includes necessary updates of
Always make a merge commit (don’t rebase/fast-forward). The merge commit will be referenced in the change log.
Rolling a New Release¶
Make sure that all changes for the new release have been merged into
masterand that tests pass. Check the CI output.
Make any other release-related changes such as adding new contributors to
CONTRIBUTORS.rstor adding missing items to
Increase the version number in
Commit the changes and push the branch. Wait for tests to run.
Make a new release by tagging the merge commit with the version number, e.g.
vX.X.X. Push the tag and wait for Travis to catch up.
make package, then
make publishto publish the source distribution and wheel to PyPI.
The documentation will be automatically be built.