When it is time for a new release of the code, here is what you have to do:
** Warning: use only three digits release numbers, e.g. 3.9.0,
Checkout the Latest development release.
Make sure version.py has the correct version number.
Make a tag in svn, using the current version number (to make sure not to include changes done by other developers in the meantime!):
svn copy -r 845 https://svn.fysik.dtu.dk/projects/ase/trunk https://svn.fysik.dtu.dk/projects/ase/tags/3.9.0 -m "Version 3.9.0"
Note the resulting tag’s revision tags_revision.
Checkout the source, specyfing the version number in the directory name:
svn co -r tags_revision https://svn.fysik.dtu.dk/projects/ase/tags/3.9.0 ase-3.9.0
Create the tar file:
cd ase-3.9.0
rm -f MANIFEST ase/svnversion.py*; python setup.py sdist
Note that the tags_revision is put into the name of the tar file automatically. Make sure that you are getting only tags_revision in the tar file name! Any changes to the source will be reflected as a mixed or modified revision tag!
Put the tar file on webX (set it read-able for all):
scp dist/python-ase-3.9.0.4465.tar.gz root@webX:/var/www/wiki/ase-files
Add a link on News and update the information on the Installation guide page and the Release notes page.
Add the new release on https://pypi.python.org/pypi/python-ase/:
Increase the version number in ase/version.py, and commit the change:
cd ~/ase
svn ci -m "Version 3.9.1"
Now the trunk is ready for work on the new version.
Send announcement email to the ase-users mailing list (see Mailing Lists).