|
| 1 | +python-blosc2 release procedure |
| 2 | +=============================== |
| 3 | + |
| 4 | +Preliminaries |
| 5 | +------------- |
| 6 | + |
| 7 | +* Make sure that the current master branch is passing the tests on Microsoft Azure. |
| 8 | + |
| 9 | +* Make sure that `RELEASE_NOTES.rst` and `ANNOUNCE.rst` are up to date with the latest news |
| 10 | + in the release. |
| 11 | + |
| 12 | +* Check that `VERSION` file contains the correct number. |
| 13 | + |
| 14 | +* Check any copyright listings and update them if necessary. You can use ``grep |
| 15 | + -i copyright`` to figure out where they might be. |
| 16 | + |
| 17 | +* Commit the changes:: |
| 18 | + |
| 19 | + git commit -a -m "Getting ready for release X.Y.Z" |
| 20 | + git push |
| 21 | + |
| 22 | +* Check that the documentation is correctly created in https://python-blosc2.rtfd.io. |
| 23 | + |
| 24 | + |
| 25 | +Tagging |
| 26 | +------- |
| 27 | + |
| 28 | +* Create a signed tag ``X.Y.Z`` from ``master``. Use the next message:: |
| 29 | + |
| 30 | + git tag -a vX.Y.Z -m "Tagging version X.Y.Z" |
| 31 | + |
| 32 | +* Push the tag to the github repo:: |
| 33 | + |
| 34 | + git push |
| 35 | + git push --tags |
| 36 | + |
| 37 | +After the tag would be up, update the release notes in: https://github.com/Blosc/python-blosc2/releases |
| 38 | + |
| 39 | +Packaging |
| 40 | +--------- |
| 41 | + |
| 42 | +* Make sure that you are in a clean directory. The best way is to |
| 43 | + re-clone and re-build:: |
| 44 | + |
| 45 | + cd /tmp |
| 46 | + git clone --recursive [email protected]:Blosc/python-blosc2.git |
| 47 | + cd python-blosc2 |
| 48 | + python setup.py build_ext |
| 49 | + |
| 50 | +* Check that all Cython generated ``*.c`` files are present. |
| 51 | + |
| 52 | +* Make the tarball with the command:: |
| 53 | + |
| 54 | + python setup.py sdist |
| 55 | + pip install dist/* |
| 56 | + |
| 57 | +Do a quick check that the tarball is sane. |
| 58 | + |
| 59 | + |
| 60 | +Uploading |
| 61 | +--------- |
| 62 | + |
| 63 | +* Register and upload it also in the PyPi repository:: |
| 64 | + |
| 65 | + twine upload dist/* |
| 66 | + |
| 67 | + |
| 68 | +It takes about 15 minutes for it to be installed using:: |
| 69 | + |
| 70 | + pip install blosc2 |
| 71 | + |
| 72 | + |
| 73 | + |
| 74 | +Announcing |
| 75 | +---------- |
| 76 | + |
| 77 | +* Send an announcement to the Blosc list. Use the ``ANNOUNCE.rst`` file as skeleton |
| 78 | + (or possibly as the definitive version). |
| 79 | + |
| 80 | +* Announce in Twitter via @Blosc2 account and rejoice. |
| 81 | + |
| 82 | + |
| 83 | +Post-release actions |
| 84 | +-------------------- |
| 85 | + |
| 86 | +* Change back to the actual python-blosc2 repo:: |
| 87 | + |
| 88 | + cd $HOME/blosc/python-blosc2 |
| 89 | + |
| 90 | + |
| 91 | +* Create new headers for adding new features in ``RELEASE_NOTES.rst`` |
| 92 | + add this place-holder: |
| 93 | + |
| 94 | + XXX version-specific blurb XXX |
| 95 | + |
| 96 | +* Edit ``VERSION`` in master to increment the version to the next |
| 97 | + minor one (i.e. X.Y.Z --> X.Y.(Z+1).dev0). |
| 98 | + |
| 99 | +* Commit your changes with:: |
| 100 | + |
| 101 | + git commit -a -m "Post X.Y.Z release actions done" |
| 102 | + git push |
| 103 | + |
| 104 | + |
| 105 | +That's all folks! |
0 commit comments