Browse Source

Fixed typos.

dev
Franco Masotti 4 years ago
parent
commit
2805e9c4a5
  1. 12
      _posts/2018-04-17-python-release-workflow.md

12
_posts/2018-04-17-python-release-workflow.md

@ -23,12 +23,12 @@ in case of a new version release with some of my Python repositories.
[ "$(echo git branch | grep "*" | tr -d '* ')" = "master" ] && echo "STOP" || echo "OK"
```
1. Finish working on the development branch (usually `dev`) and commit
2. Finish working on the development branch (usually `dev`) and commit
1. `git add -A`
2. `git commit -am "$commit_message"`
3. `git push`
2. Update version numbers and do all necessary verifications
3. Update version numbers and do all necessary verifications
1. update version numbers in:
- `./setup.py`
- `./docs/conf.py`
@ -45,7 +45,7 @@ in case of a new version release with some of my Python repositories.
11. `git commit -am "Preparing for new release."`
12. `git push`
3. Update the documentation
4. Update the documentation
1. `make doc`
2. `cp -aR docs/_build/html ~`
3. `git checkout gh-pages`
@ -55,15 +55,15 @@ in case of a new version release with some of my Python repositories.
7. `git commit -am "New release."`
8. `git push`
4. Merge the `$dev_branch` branch into `master` and create a new annotated git tag
5. Merge the `$dev_branch` branch into `master` and create a new annotated git tag
1. `git checkout master`
2. `git merge $dev_branch`
3. `git tag -a $version_id -m "New release."`
4. `git push`
5. `git push origin $version_id`
5. Upload the package to PIP
6. Upload the package to PIP
1. `make dist`
2. `make upload`
6. Update downstream districution packages (eg: `PKGBUILD` files).
7. Update downstream districution packages (eg: `PKGBUILD` files).

Loading…
Cancel
Save