| 1 | | [[PageOutline]] |
| 2 | | |
| 3 | | Beginning August 2007, Jarrod Millman is the !SciPy Release Manager (RM). The RM |
| 4 | | we will create a stable branch every 3 months. |
| 5 | | |
| 6 | | 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, ... |
| 7 | | |
| 8 | | Understanding the version numbering: |
| 9 | | || 0.6.0 || a major stable releases || |
| 10 | | || 0.6.X || the first maintenance releases (bugfixes only) || |
| 11 | | || 0.6.1.dev3432 || version 3432 of the development branch leading to 0.6.1 || |
| 12 | | || 0.7.0.dev3532 || version 3532 of the development trunk leading to 0.7 || |
| 13 | | |
| 14 | | To make a "release" of !SciPy, the release manager should follow these steps: |
| 15 | | |
| 16 | | = Prepare for upcoming release = |
| 17 | | 1. Announce upcoming release on the developer's list. |
| 18 | | * introduce a soft-freeze |
| 19 | | 1. Create a release branch (if none exists). |
| 20 | | * {{{svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/branches/<version> -m "Create a release branch."}}} |
| 21 | | * increment version number in {{{trunk/scipy/version.py}}} |
| 22 | | |
| 23 | | = Review the state of the branch = |
| 24 | | 1. Make sure the current trunk builds a package correctly: |
| 25 | | 1. All tests should pass. |
| 26 | | |
| 27 | | = Create the release tag from the branch = |
| 28 | | 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."}}} |
| 29 | | 1. increment version number in {{{branches/<version>/scipy/version.py}}} |
| 30 | | 1. use {{{new_manifest.sh}}} update the {{{MANIFEST.in}}} in {{{tags/<version>/scipy/version.py}}} |
| 31 | | 1. set {{{release=True}}} in {{{tags/<version>/scipy/version.py}}} |
| 32 | | |
| 33 | | = Create source files and binary packages = |
| 34 | | 1. Check out the tagged version |
| 35 | | 1. Make the distribution tar-files and binary releases and |
| 36 | | 1. Create the distribution (eggs) |
| 37 | | 1. Create a Windows binary release |
| 38 | | 1. Test the releases |
| 39 | | |
| 40 | | = Release on sourceforge site = |
| 41 | | 1. Create a release announcement |
| 42 | | * list major changes |
| 43 | | * create checksums using md5sum |
| 44 | | 1. Up-load files to [http://sourceforge.net/projects/scipy SourceForge] |
| 45 | | |
| 46 | | = Update the websites = |
| 47 | | 1. Update scipy.org wiki |
| 48 | | 1. Update the roadmap |
| 49 | | 1. Update the [wiki:APIDocumentation] |
| 50 | | 1. Update [http://pypi.python.org/pypi/numpy Python Package Index] |
| 51 | | |
| 52 | | = Announce the release = |
| 53 | | 1. Send an email to the !NumPy developer's list |
| 54 | | 1. Send an email to the !SciPy lists |
| 55 | | 1. Send an email to python-annouce |
| | 1 | The release process for Scipy is currently (March 2011) almost identical to the Numpy process. We aim to release a new stable version every six months. The release process is documented in detail at https://github.com/numpy/numpy/blob/master/doc/HOWTO_RELEASE.rst.txt |
