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

One week before:

1. Notify Moodle developers and Moodle Partners about the upcoming release
2. Freeze stable development
3. Test / QA / etc

Release day:

1. cvs -q update -dP
2. Edit version.php, update name and version to new point release and commit
3. cvs tag -F MOODLE_XX_MERGED version.php
4. cvs tag -FR MOODLE_XXY to tag everything in the release
5. Optional: In case of repackaging of release (due to some critical cause), move also the weekly with cvs tag -FR MOODLE_XX_WEEKLY, that way people using weeklies from cvs, will update to latest (correct) version sooner.
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 the version.php in CVS to be X.X.Y+
13. cvs tag -F MOODLE_XX_MERGED version.php
14. Update filters (like Moodle 1.8.x bugs) in the tracker to include new unreleased versions
15. Make sure the Release Notes page is updated
16. Add new version on the Release page
17. Notify all registered sys admins

One week later:

1. Add all security notices to Security news
2. Add all security notices to the Release Notes page
3. Post about the release on Moodle.org front page