# html pages scp index.html jdh2358@matplotlib.sf.net:/home/groups/m/ma/matplotlib/htdocs # project page http://sourceforge.net/projects/matplotlib # home page http://matplotlib.sourceforge.net ### updating the website # build the docs mother> cd ~/python/projects/matplotlib mother> make htmldocs mother> cd htdocs mother> python process_docs.py mother> python convert.py mother> tar cvfz site.tar.gz *.html screenshots tut examples mother> scp site.tar.gz jdh2358@matplotlib.sf.net:/home/groups/m/ma/matplotlib/htdocs/ mother> ssh -l jdh2358 shell.sf.net sf> cd /home/groups/m/ma/matplotlib/htdocs sf> tar xvfz site.tar.gz ### Doing a release 0) Turn off all the build flags 0) Testing: remove font cache and test w/ and w/o font cache on some example script 0) Testing: Run examples/backend_driver.py w/o errors; run the backend specific demos (object_picker, anim , embedding*). Do an explicity numarray and python2.2 test. 0) Remove MANIFEST so it will be rebuilt by MANIFEST.in 0) Make sure sdist builds setuptools-compatible release: Remove setup.cfg (or, if more than the [egg_info] section is in this file, remove the [egg_info] section). See http://mail.python.org/pipermail/distutils-sig/2006-July/006561.html for more info. 1) Comment out all the savefig commands in the examples dir > rfr -f savefig -r '#savefig' *.py > rfr -f '##savefig' -r '#savefig' *.py 2) edit __init__.py, setup.py license.html.template to the correct version number local> clearbak local> make htmldocs local> scp site.tar.gz jdh2358@matplotlib.sf.net:/home/groups/m/ma/matplotlib/htdocs/ local> ssh -l jdh2358 shell.sf.net sf> cd /home/groups/m/ma/matplotlib/htdocs sf> tar xvfz site.tar.gz > make release > build on win32 (set the backend to tkagg, set the 'auto' flags in setup.py to 1, set tk windowing) > cvs tag the sucker 4) anon ftp the tar.gz and exe file to SF local> cd dist local> ncftp upload.sourceforge.net ncftp> cd incoming ncftp> put tar.gz, zip exe 5) go to https://sourceforge.net/project/admin/?group_id=80706 and do a file release. Click on the "Admin" tab to log in as an admin, and then the "File Releases" tab. Go to the bottom and click "add release" and enter the package name but not the version number in the "Package Name" box. You will then be prompted for the "New release name" at which point you can add the version number, eg somepackage-0.1 and click "Create this release". You will then be taken to a fairly self explanatory page where you can enter the Change notes, the release notes, and select which packages from the incoming ftp archive you want to include in this release. For each binary, you will need to select the platform and file type, and when you are done you click on the "notify users who are monitoring this package link" Standard reminders for numarray build - change numerix in matplotlibrc *and* setup.py - change backend to tkagg in rc - email users monitoring the package and me when you are done and I'll send the announcement Trove categorization is under Public info on the admin page standard reminders for win32 - setup flags to 1 - backend tkagg in rc - unix2dos the rc file