Release process

    Give a new release version number by fair dice roll
    Update setup.py with the new version number
    Update CHANGES.txt with the version number and the release date
    Commit changes to trunk

3. Release

    Tag the release in the version control system
    Checkout the tag into a clean folder
    Run necessary scripts to build binary files for the distribution (like .mo files – more about this later)
    Create a package (python setup.py sdist)
    Upload the package to PyPi (python setup.py upload)
    Tag and upload new documentation

3. Postrelease

    Update setup.py with the next version development version number and development tag in the version (-dev, -trunk)
    Create a fresh change log entry in CHANGES.txt where you start collecting changes for the next release
    Commit to the trunk