-
Notifications
You must be signed in to change notification settings - Fork 42
Releasing ramp workflow
Joris Van den Bossche edited this page Nov 6, 2017
·
2 revisions
-
Update the changelog:
- Change the "Unreleased" to the new version, and add a new empty unreleased section
- Make just this change in a single commit: eg
git commit -m "Release 0.2.0"
- Example commit: https://github.com/paris-saclay-cds/ramp-workflow/commit/167db887b48fa48646f02bebc36499641c14c342
- Push this commit to master, or more safely: go through the PR process
-
Tag this commit on master with the new version number:
- Make sure you updated your local master branch (after the steps above)
- Make sure you are on the release commit from above (check with
git log
) - Tag that commit: eg
git tag -a v0.2.0 -m "Version 0.2.0"
- Push this commit to github:
git push --tag
That's all. Now a new release will be available on github and rampwf.__version__
will indicated the new version number.
(TODO: we should update this with how to upload to PyPI once we do this)
Copyright (c) 2014 - 2018 Paris-Saclay Center for Data Science (http://www.datascience-paris-saclay.fr/)