Releasing

This page is a guide to releasing new versions of Oscar. It's documented as there are quite a few things to do.

These are the steps involved:

Before pushing to PyPI:

Make sure the tests pass (obviously)
Ensure that any new migrations are correctly numbered (ie there are no apps with two migrations using the same number). You can view the migrations committed since a tag using:
```
  git log --name-status 0.3.. | grep migration 
```
Update the CHANGELOG with details of the new release, including any relevant upgrading notes
Browse the questions asked on the mailing list and consider writing new documentation recipes to cover these cases. This is a good way of improving the documentation.

Push to PyPI:

./setup.py sdist upload

Tweet about it via @django_oscar
Email mailing list with link to release notes
Update readthedocs to use the new version as the latest (only relevant for major version bumps)
Update Google Drive stats
Update oscarcommerce.com
Clean up remote branches that are no longer needed. Delete with:
```
  git push origin :branch-to-delete
```

Have a banana!

Provide feedback