ReleaseProcess

How to make a CP release

This wiki is being converted to a release script as ./release.py in the source tree.

Test the source

  • Run the tests with `nosetests -s -v test`.
  • You should probably do 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, 2.5, 2.7, and 3.2.

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
  • 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.

Updated

Tip: Filter by directory path e.g. /media app.js to search for public/media/app.js.
Tip: Use camelCasing e.g. ProjME to search for ProjectModifiedEvent.java.
Tip: Filter by extension type e.g. /repo .js to search for all .js files in the /repo directory.
Tip: Separate your search with spaces e.g. /ssh pom.xml to search for src/ssh/pom.xml.
Tip: Use ↑ and ↓ arrow keys to navigate and return to view the file.
Tip: You can also navigate files with Ctrl+j (next) and Ctrl+k (previous) and view the file with Ctrl+o.
Tip: You can also navigate files with Alt+j (next) and Alt+k (previous) and view the file with Alt+o.