| 3 | | 1) Make sure the current trunk builds a package correctly: |
| 4 | | |
| 5 | | - python setup.py bdist usually works |
| 6 | | - python setup.py sdist followed by trying to build the package is another option |
| 7 | | |
| 8 | | 2) Create the release "tag" |
| 9 | | |
| 10 | | - svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/tags/<version> |
| 11 | | |
| 12 | | 3) Update the version of the trunk |
| 13 | | |
| 14 | | - Change the scipy/version.py file to bump up the release number to the next release |
| 15 | | |
| 16 | | 4) Update the version of the tag |
| 17 | | |
| 18 | | - Switch to the tagged tree (svn switch http://svn.scipy.org/svn/scipy/tags/<version> |
| 19 | | - Update the scipy/version.py by changing the released line to True |
| 20 | | |
| 21 | | 5) Make the distribution tar-files and binary releases and up-load them to [http://sourceforge.net/projects/scipy SourceForge] |
| | 3 | 1. Make sure the current trunk builds a package correctly: |
| | 4 | {{{ |
| | 5 | python setup.py bdist |
| | 6 | python setup.py sdist |
| | 7 | }}} |
| | 8 | 1. Create the release "tag" |
| | 9 | {{{ |
| | 10 | svn cp http://svn.scipy.org/svn/scipy/trunk http://svn.scipy.org/svn/scipy/tags/<version> |
| | 11 | }}} |
| | 12 | 1. Update the version of the trunk |
| | 13 | - Increment the release number in {{{scipy/version.py}}} |
| | 14 | 1. Update the version of the tag |
| | 15 | - Switch to the tag {{{svn switch http://svn.scipy.org/svn/scipy/tags/<version>}}} |
| | 16 | - Set {{{release=True}}} in {{{scipy/version.py}}} |
| | 17 | 1. Make the distribution tar-files and binary releases and up-load them to [http://sourceforge.net/projects/scipy SourceForge] |
