Release procedure

Release candidate procedure:

1. Make sure all submodules are at master and that tests pass.
2. Release notes: to be placed on the wiki and distributed to mailing lists
3. Edit changelog in clawpack/changes.md (Extended annotated review of major pull requests and commits)
4. Update/commit version number in clawpack/clawpack/setup.py, remove all others

    vim setup.py
        MAJOR               = 5
        MINOR               = 0
        MICRO               = 0
        TYPE                = 'rc-alpha'
    git add setup.py
    git commit

1. Update version number in doc/doc/conf.py and upload to clawpack.github.com

    cd doc/doc
    vim conf.py
        version = 5.0
        release = 5.0.0rc-alpha
    save conf.py
    make html
    git add conf.py
    git commit
    bash rsync_clawpack.github.sh

1. Upload documentation to GitHub

    cd clawpack/clawpack.github.com
    git commit -a
    git push

1. Tag commit to match version number in setup.py

    cd clawpack
    git tag -a 5.0.0rc-alpha
    git push --tags

1. Roll tarball and any other formats

# brew install git-archive-all
git-archive-all clawpack-rc-alpha.tar
gzip clawpack-rc-alpha.tar

1. Upload tarballs/binaries to GitHub

https://github.com/clawpack/clawpack/releases
Drag and drop tar.gz file.

1. Update PyPI

git branch -b 5.0.x
git add setup.py
# add new download_url
git push clawpack 5.0.x:5.0.x
python setup.py register

1. Announce to claw-dev
2. Close any issues that arise
3. Repeat until issues stop arising

Proper release procedure:

1. Roll conda, hashdist, other installers
2. Announce release notes to mailing lists

References: An Example PyPI Project