1 # Releasing datasette-pytables
3 Author: Javier Sancho, Francesc Alted
4 Contact: jsf@jsancho.org, francesc@blosc.org
10 * Make sure that ``RELEASE_NOTES.md`` and ``ANNOUNCE.md`` are up to
11 date with the latest news in the release.
13 * Commit your changes:
16 $ git commit -a -m"Getting ready for X.Y.Z final"
19 * Once a year: check that the copyright year in `LICENSE` file.
24 * Create a tag ``X.Y.Z`` from ``master``. Use the next message:
27 $ git tag -a X.Y.Z -m "Tagging version X.Y.Z"
30 Note: For release candidates, just add a rcN suffix to tag ("X.Y.ZrcN").
32 * Or, alternatively, make a signed tag (requires gpg correctly configured):
35 $ git tag -s X.Y.Z -m "Tagging version X.Y.Z"
38 * Push the tag to the Github repo:
48 * Go to the root directory and run:
57 * Make sure that you are in a clean directory. The best way is to
58 re-clone and re-build:
62 $ git clone https://github.com/PyTables/datasette-pytables
63 $ cd datasette-pytables
64 $ python setup.py build
67 * Make the tarball with the command:
70 $ python setup.py sdist
73 Do a quick check that the tarball is sane.
78 * Upload it also in the PyPi repository:
81 $ python setup.py sdist upload
87 * Send an announcement to the python-announce, python-users and pydata
88 lists. Use the ``ANNOUNCE.md`` file as skeleton (or possibly as
89 the definitive version).
91 * Tweet about the new release and rejoice!
94 ## Post-release actions
96 * Create new headers for adding new features in ``RELEASE_NOTES.rst``
97 and add this place-holder instead:
99 #XXX version-specific blurb XXX#
101 * Commit your changes with:
104 $ git commit -a -m"Post X.Y.Z release actions done"