Releasing Binaries

Below is the reminder of the steps to follows, and the associated shell commands:

  1. Ensure that all tests pass just fine with python test. If you have several installation of python on your machine, use tox, to run the test using Py32, Py33 and Py34.

  2. Commit and push all changes necessary to get the tests to pass.

  3. Release using python release --type=micro. The setup script handles both the version number and the tagging process. The 'type' option specifies whether we are doing a major, minor, or a micro release. It also publish automatically both the source and egg distribution on Pypi. As a reminder, below are the commands to publish manually on Pypi. You must have an account on both the Pypi server and the test server, and the associated credentials in the ~\.pypirc. More details are available in this tutorial.

    1. Try to register the project on pipy python register -r pypitest. Remove any error reported until the registration is a full success.

    2. Try to upload the binaries python sdist upload -r pypitest

    3. Once it works on the test server, you can do the same on Pypi Live, using python register -r pypi for registration and python sdist upload -r pypi

  4. Push the changes using git push --follow-tags. Pushing manually permits to easily back-off if the release process fails.

  5. Create a new release, specifying the tag and upload the appropriate binaries from ./dist on the GitHub release page. Note that Git can provide you with a summary of the changes made since the last release: git log --online --decorate v0.4.1..HEAD

Publishing the Documentation

To update the documentation — this very website — follows the following commands. You may want to check out the documentation of MkDocs.

  1. Update the markdown documentation as needed (see files in doc/docs)

  2. Build the website using mkdocs build --clean. This will prepare the content to be uploaded

  3. Publish the web site using python upload_docs --upload-dir=site