Development:Release process: Difference between revisions
From MoodleDocs
No edit summary |
|||
Line 6: | Line 6: | ||
# '''cvs -q update -dP''' | # '''cvs -q update -dP''' | ||
# Edit version.php, update name and version to new point release and commit | # Edit version.php, update name and version to new point release and commit | ||
# '''cvs tag -F MOODLE_XX_MERGED version.php''' | # '''cvs tag -F MOODLE_XX_MERGED version.php''' | ||
# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release | |||
# '''cvs -q update -dP''' all code on download server | # '''cvs -q update -dP''' all code on download server | ||
# Run moodle-makenightlystableXX | # Run moodle-makenightlystableXX |
Revision as of 07:31, 15 October 2008
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
- cvs -q update -dP
- Edit version.php, update name and version to new point release and commit
- cvs tag -F MOODLE_XX_MERGED version.php
- cvs tag -FR MOODLE_XXY to tag everything in the release
- 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.
- Update filters (like Moodle 1.8.x bugs) in the tracker to include new unreleased versions
- Make sure the Release Notes page is updated
- Make sure all security bugs are posted on Security news
- Add new version on the Release page
- Post about the release on Moodle.org front page
- Update the version.php in CVS to be X.X.Y+
- cvs tag -F MOODLE_XX_MERGED version.php