1 # Releasing datasette-pytables
3 Author: Javier Sancho, Francesc Alted
4 Contact: jsf@jsancho.org, francesc@blosc.org
10 * Update the version number at ``VERSION`` and ``ANNOUNCE.md``.
12 * Make sure that ``RELEASE_NOTES.md`` and ``ANNOUNCE.md`` are up to
13 date with the latest news in the release.
15 * Commit your changes:
18 $ git commit -a -m"Getting ready for X.Y.Z final"
21 * Once a year: check that the copyright year in `LICENSE` file.
26 * Create a tag ``vX.Y.Z`` from ``master``. Use the next message:
29 $ git tag -a vX.Y.Z -m "Tagging version X.Y.Z"
32 Note: For release candidates, just add a rcN suffix to tag ("vX.Y.ZrcN").
34 * Or, alternatively, make a signed tag (requires gpg correctly configured):
37 $ git tag -s vX.Y.Z -m "Tagging version X.Y.Z"
40 * Push the tag to the Github repo:
50 * Go to the root directory and run:
59 * Make sure that you are in a clean directory. The best way is to
60 re-clone and re-build:
64 $ git clone https://github.com/PyTables/datasette-pytables
65 $ cd datasette-pytables
66 $ python setup.py build
70 * Make the tarball with the command:
73 $ python setup.py sdist
76 Do a quick check that the tarball is sane.
81 * Upload it also in the PyPi repository:
84 $ python setup.py sdist upload
90 * Send an announcement to the pytables-announce, pytables-users and pydata
91 lists. Use the ``ANNOUNCE.md`` file as skeleton (or possibly as
92 the definitive version).
94 * Tweet about the new release and rejoice!
97 ## Post-release actions
99 * Create new headers for adding new features in ``RELEASE_NOTES.rst``
100 and add this place-holder instead:
102 #XXX version-specific blurb XXX#
104 * Update ``VERSION`` file to X.Y.(Z+1)-dev
106 * Commit your changes with:
109 $ git commit -a -m"Post X.Y.Z release actions done"