How to make a CP release
Test the source
- Run python test.py and python test.py --1.0.
- Starting with the 3.0 branch, you should probably do python test.py --ssl, too.
- Test it on Windows, Linux, and Mac (solicit help from the friendly users on #cherrypy).
- Our setup.py says we require Python 2.3. You should probably test on at least 2.4.x, 2.5.x, and 2.6.x. Starting in CP 3.2, test the python3 branch for Python 3.x releases.
Document the source code
- Change version # in __init__.py, setup.py, wsgiserver/__init__.py.
- Change development status in setup.py if necessary.
- Change the download_url in setup.py to reflect the new version.
- Checkin changes
- Tag the source tree
Create distros
- Run ./make-sdist (it is nice to have *.gz and .zip versions).
- On Windows, run python setup.py sdist --format=zip and python setup.py bdist --format=wininst.
Publish distros
- Upload it to download.cherrypy.org.
- Have a few friendly souls on the IRC channel test the released files.
- python setup.py register
Make sure you go to pypi and reactivate any older versions that you want to remain visible there as well (and installable via easy_install). Register seems to deactivate all other versions.(This seems to be fixed now with the new "Auto-hide old releases" option). - Do a test of installing the distro with easy_install CherryPy.
Tell everybody
- Change Wiki: Home page (news), CherryPyDownload.
- Announce it on newsgroups, mailing lists, IRC /topic etc.
