Author: | Francesc Alted |
---|---|
Contact: | [email protected] |
Date: | 2012-09-16 |
- Make sure that
RELEASE_NOTES.rst
andANNOUNCE.rst
are up to date with the latest news in the release. - Check that
VERSION
file contains the correct number.
- After compiling, run:
$ PYTHONPATH=. (or "set PYTHONPATH=." on Win) $ export PYTHONPATH=. (not needed on Win) $ python blosc/toplevel.py (add -v for verbose mode)
- Run the test suite in different platforms (at least Linux and Windows) and make sure that all tests passes.
Make the tarball with the command:
$ python setup.py sdist
Do a quick check that the tarball is sane.
Make the binary packages for supported Python versions (2.6 and 2.7 currently). Check that installer works correctly.
Go to the downloads section of the python-blosc project in github and upload the source tarball and the binary packages.
Register and upload it also in the PyPi repository:
$ python setup.py sdist upload $ python setup.py register
Create a tag
X.Y.Z
frommaster
. Use the next message:$ git tag -a vX.Y.Z -m "Tagging version X.Y.Z"
Push the tag to the github repo:
$ git push --tags
Update the release notes in the python-blosc site:
https://github.com/FrancescAlted/python-blosc/wiki/Release-notes
Send an announcement to the blosc, numpy list and python-announce lists. Use the
ANNOUNCE.rst
file as skeleton (or possibly as the definitive version).
Edit
VERSION
in master to increment the version to the next minor one (i.e. X.Y.Z --> X.Y.(Z+1).dev).Create new headers for adding new features in
RELEASE_NOTES.rst
and empty the release-specific information inANNOUNCE.rst
and add this place-holder instead:#XXX version-specific blurb XXX#
That's all folks!