As of August 2007, 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, ...

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

Prepare for upcoming release

1. Send an email to scipy-dev@… indicating the release is about to start.

Review the state of the source tree

1. Make sure the current trunk builds a package correctly:

   python setup.py bdist
   python setup.py sdist
   

Create a release branch (optional)

1. Create the branch

   svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/branches/<version>
   

2. Increment the release number of the trunk:

   http://svn.scipy.org/svn/scipy/trunk/scipy/version.py
   

Create the release tag

1. Create a tag off the branch

   svn cp http://svn.scipy.org/svn/scipy/branches/<version> http://svn.scipy.org/svn/scipy/tags/<version>
   

2. Update the version of the
   • Switch to the tag svn switch http://svn.scipy.org/svn/scipy/tags/<version>
   • Set release=True in scipy/version.py

Check out the tagged version

Create the distribution (eggs)

Create a Windows binary release

Test the releases

Update the SourceForge site

1. Make the distribution tar-files and binary releases and up-load them to SourceForge

Update scipy.org wiki

Announce the release