Beginning August 2007, Jarrod Millman is the SciPy Release Manager (RM). The RM we will create a stable branch every 3 months.

Development will continue on the trunk and we will tag off the branch only as needed to address bugs. For more specific details about the roadmap see milestone:0.6, milestone:0.7, ...

Understanding the version numbering:

0.6.0	a major stable releases
0.6.X	the first maintenance releases (bugfixes only)
0.6.1.dev3432	version 3432 of the development branch leading to 0.6.1
0.7.0.dev3532	version 3532 of the development trunk leading to 0.7

To make a "release" of SciPy, the release manager should follow these steps:

Prepare for upcoming release

1. Announce upcoming release on the developer's list.
   • introduce a soft-freeze
2. Create a release branch (if none exists).
   • svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/branches/<version> -m "Create a release branch."
   • increment version number in trunk/scipy/version.py

Review the state of the branch

1. Make sure the current trunk builds a package correctly:
2. All tests should pass.

Create the release tag from the branch

1. svn cp http://svn.scipy.org/svn/scipy/branches/<version> http://svn.scipy.org/svn/scipy/tags/<version> -m "Create the new release tag."
2. increment version number in branches/<version>/scipy/version.py
3. use new_manifest.sh update the MANIFEST.in in tags/<version>/scipy/version.py
4. set release=True in tags/<version>/scipy/version.py

Create source files and binary packages

1. Check out the tagged version
2. Make the distribution tar-files and binary releases and
3. Create the distribution (eggs)
4. Create a Windows binary release
5. Test the releases

Update the websites

1. Up-load files to SourceForge
2. Update scipy.org wiki
3. Update the roadmap

Announce the release

1. Send an email to the NumPy developer's list
2. Send an email to the SciPy lists
3. Send an email to python-annouce