This is a list of things that developers should do when preparing a new release of 4Suite.
Before release:
- Close any bugs on SourceForge that have been resolved or that are unreproducible, out of date, etc.
- Update docs/KNOWN-BUGS.txt to match bugs still open on SourceForge. Make sure the date and version number in the file are current.
- Check top-level README, docs/xml/HowTos/UNIX.doc, and docs/xml/HowTos/Windows.doc for accuracy, especially taking note of the version numbers of dependencies like Python and PyXML.
- If possible, on Windows and Unix, run the test suites and seek to resolve any issues that should be resolved before release. Try to do it with 4Suite installed under both the oldest and newest supported versions of Python.
- When running the test suites, use "full" mode so that all drivers are tested: 'python test.py -v --full' (Of course, it helps to have all of the driver dependencies, like PostgreSQL, installed.)
- Also note that the test suites expect to be run as a superuser, from the installed test suite directory.
- Do a '4ss manager init' and '4ss_manager start'. Watch for any errors in the log file. Click through the HTTP demos on port 8801 and make sure they aren't broken. Make sure the Dashboard at least comes up on port 8800.
During release:
- Add downloadables to ftp.4suite.org FTP site.
- Add downloadables to SourceForge project.
- On 4Suite.org...
- Update rdf/software.rdf to reference new downloadables;
- Update static/README to be a copy of current README;
- Update static/timeline.html as necessary;
- Upgrade 4Suite itself so new HowTo docs will be picked up.
- Remember to commit changes to CVS!
- Announce release on 4suite-ann, 4suite, SourceForge, and other lists/forums.
- Update freshmeat.net.
After release:
- Bump the 4Suite version number in setup.py.