Development:Release process
From MoodleDocs
Some notes on the release process, to be fleshed out.
For a stable release on an existing branch XX with point value Y
- Test / QA / etc
- Edit version.php, update name and version to new point release and commit
- cvs tag -F MOODLE_XXY version.php
- cvs tag -F MOODLE_XX_MERGED version.php
- cvs -q update -dP all code on download server
- Run moodle-makenightlystableXX
- Go to download/stableXX
- Copy current daily as release package:
- cp moodle-latest-XX.zip moodle-X.X.Y.zip
- cp moodle-latest-XX.tgz moodle-X.X.Y.tgz
- Edit download index.php page with new release info and links
- Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release.
- Make sure the release notes page is updated Release
- Update the version.php in CVS to be X.X.Y+
- cvs tag -F MOODLE_XX_MERGED version.php