How to make a release

• Write the changelog (doc/whats_new.rst). Commit counts can be generated using git log <last_release>.. | git shortlog -s -n

• Fix Milestone issues

• Compile documentation, make sure all examples compile.

• Run the tests from the last release to see that all deprecations have been taken care of.

• Tag master with X.X-branching

• Create a new branch X.X. Next step for both branches separately (once with -git, once without)

• Change the version number hardcoded in web page: doc/themes/scikit-learn/layout.html

• Change the version number in

  • doc/conf.py

  • sklearn/__init__.py

• check on python 2.6, 2.7, 3k

• Tag X.X branch as X.X.

• then python setup.py sdist will create a .tar.gz in the dist/ directory.

• untar and test it

• upload packet and website to sourceforge (see doc/README).

• using sftp make 'stable' link to the new release.

• Set the default download to the new release.

• upload to PyPi with python setup.py sdist upload (you might need to python setup.py register first)

• hide the old version on the PyPi website

• Update the mloss page: https://mloss.org/software/view/240/ (right now, Fabian and Andy are the only ones that can do that).

• remove all deprecated features from dev that are to be removed in the next version.

• Update the wikipedia page with the latest stable version (should we?)