Browse Source

Updated post.

dev
Franco Masotti 3 years ago
parent
commit
ea0427e6c2
  1. 33
      _posts/2018-04-16-my-python-release-workflow.md

33
_posts/2018-04-16-my-python-release-workflow.md

@ -1,7 +1,7 @@
---
title: My Python release workflow
tags: [python, git, workflow]
updated: 2019-03-18 18:31
updated: 2019-04-14 17:06
description: A personal reminder with the instructions for releasing new versions of Python packages
---
@ -28,22 +28,29 @@ in case of a new version release with some of my Python repositories.
2. `git commit -am "$commit_message"`
3. `git push`
3. Update version numbers and do all necessary verifications
3. Update version numbers, requirements, and do all necessary verifications
1. update version numbers in:
- `./setup.py`
- `./docs/conf.py`
- any file in the `./packages` directory.
2. `make pep`
3. `make test`
4. `sudo make install`
5. `cd ~ && python`
6. `import $package_name`
7. `cd $OLDPWD`
8. `sudo make uninstall`
9. `make clean`
10. `git add -A`
11. `git commit -am "Preparing for new release."`
12. `git push`
2. update the `./requirements.txt` file with the appropriate packages.
3. `sudo pip install -r requirements.txt`
4. `make pep`
5. `make test`
6. `sudo make install`
7. `cd ~ && python`
8. `import $package_name`
9. `cd $OLDPWD`
10. `sudo make uninstall`
11. `make clean`
12. Update copyright years, emails, contributors if necessary in:
- `./README.rst`
- `./docs/conf.py`
- `./docs/copyright_license.rst`
- all Python source files.
13. `git add -A`
14. `git commit -am "Preparing for new release."`
15. `git push`
4. Update the documentation
1. `make doc`

Loading…
Cancel
Save