## Cutting a new pypi release: The case of django-councilmatic

Have you and your friends been making lots of changes to django-councilmatic? are you ready to cut a new release in pypi?
Take these steps.

* Summarize your changes in `RELEASENOTES.md`.

* On a branch, visit `setup.py` and adjust the version of django-councilmatic, e.g. version='0.6.9' becomes version='0.6.10'

* Push changes to GitHub and merge.

* Locally, return to master, and pull changes down.

* Run `python setup.py sdist`- it will create a new distribution in a `dist` directory.

* You should be in a virtualenv that has twine installed. In not, then install it: `pip install twine`.

* Then, upload this release to pypi:

```
twine upload dist/<name dist file>
```

You can see your new version on pypi.python.org!

***

N.B. For all this to work, you need a .pypirc file in your home directory (`/Users/<username>`). Add the following:

```
[distutils]
index-servers =
  pypi

[pypi]
username:<username>
password:<your password>
```