git checkout master
git pull
Update swiftly/__init__.py VERSION string to an even-ending version
git add swiftly/__init__.py
git commit -m 'Releasing <version>'
git tag <version>

rm -rf doc/build/*
python setup.py build_sphinx
git checkout gh-pages
mv doc/build/html <version>
git add <version>
Update index.html to point to new release docs
git add index.html
git commit -m 'Generated <version> docs'

git checkout debian
git merge master
Update debian/changelog
git add debian/changelog
git commit -m 'Releasing <version>'

git checkout rpm
git merge master
Update rpmbuild/SPECS/swiftly.spec Version: line and %changelog area
git add rpmbuild/SPECS/swiftly.spec
git commit -m 'Releasing <version>'

git checkout master
Update swiftly/__init__.py VERSION string to an odd-ending version
git add swiftly/__init__.py
git commit -m 'Moving to <version> development'

rm -rf doc/build/*
python setup.py build_sphinx
git checkout gh-pages
rm -rf dev
mv doc/build/html dev
git add dev
git commit -m 'Updated dev docs'

git checkout master
git push
git push --tags

Update PyPI; however you magically figure out how to do that. I think I edited
the past version's information, changing the version number, and it created a
new entry that I could then upload a source tar.gz to.
