Releasing a new version
-----------------------

* Run tests: python setup.py test
  [don't forget to run with Python 2.7 and 3.4]

* Bump version in yapf/__init__.py

* Build source distribution: python setup.py sdist

* Check it looks OK, install it onto a virtualenv, run tests, run yapf as a tool

* Push to PyPI: python setup.py sdist bdist_wheel upload

* Test in a clean virtualenv that 'pip install yapf' works with the new version

* Commit the version bump; add tag with git tag v<VERSION_NUM>; git push --tags

TODO: discuss how to use tox to make virtualenv testing easier.

Running YAPF on itself
----------------------

The run YAPF on all of YAPF::

 $ PYTHONPATH=$PWD/yapf python -m yapf -i -r .

The run YAPF on just the files changed in in the curent git branch::

 $ PYTHONPATH=$PWD/yapf python -m yapf -i $(git diff --name-only @{upstream})

Releasing a new version
-----------------------

* Run tests: python setup.py test
  [don't forget to run with Python 2.7 and 3.4]

* Bump version in yapf/__init__.py

* Build source distribution: python setup.py sdist

* Check it looks OK, install it onto a virtualenv, run tests, run yapf as a tool

* Push to PyPI: python setup.py sdist bdist_wheel upload

* Test in a clean virtualenv that 'pip install yapf' works with the new version

* Commit the version bump; add tag with git tag v<VERSION_NUM>; git push --tags

TODO: discuss how to use tox to make virtualenv testing easier.

Add docs on how to run YAPF on itself
Add docs on how to run YAPF on itself

Ideally we should also provide a tools (or docs) on how
to run YAPF on the just the parts of the file changes
on a git branch (a la chromium's 'git cl format').
