Development:Release process

Some notes on the release process, to be fleshed out.

For a stable release on an existing branch XX with point value Y

1. Test / QA / etc
2. cvs -q update -dP
3. Edit version.php, update name and version to new point release and commit
4. cvs tag -FR MOODLE_XXY version.php
5. cvs tag -F MOODLE_XX_MERGED version.php
6. cvs -q update -dP all code on download server
7. Run moodle-makenightlystableXX
8. Go to download/stableXX
9. Copy current daily as release package:
   1. cp moodle-latest-XX.zip moodle-X.X.Y.zip
   2. cp moodle-latest-XX.tgz moodle-X.X.Y.tgz
10. Edit download index.php page with new release info and links
11. Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release.
12. Update filters (like Moodle 1.8.x bugs) in the tracker to include new unreleased versions
13. Make sure the Release Notes page is updated
14. Add new version on the Release page
15. Update the version.php in CVS to be X.X.Y+
16. cvs tag -F MOODLE_XX_MERGED version.php