What do you think about putting the following processes in place:
- Update the documentation automatically in a central place. It shall only be necessary to edit the documentation XML file of the stable release and get the documentation generated in HTML and committed to CVS. Someone keen on writing a BASH script to do this ?
- The release begins by updating openacs.org to that release. Once this is done publish the release. But maybe Joel can post the steps necessary to cut the release (once the branch is deemed release worthy).
This way we find more bugs that annoy us and fix them as all of us are using openacs.org. And the documentation is easier to maintain, thereby making it more likely for people to maintain it in the first place.
