Development:Release process: Difference between revisions
From MoodleDocs
(Add on Release page) |
(Update filters in the tracker) |
||
| Line 16: | Line 16: | ||
# Edit download index.php page with new release info and links | # 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. | # Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release. | ||
# Make sure the [[ | # Update filters (like Moodle 1.8.x bugs) in the tracker to include new unreleased versions | ||
# Make sure the [[Release Notes]] page is updated | |||
# Add new version on the [[Release]] page | # Add new version on the [[Release]] page | ||
# Update the version.php in CVS to be X.X.Y+ | # Update the version.php in CVS to be X.X.Y+ | ||
# '''cvs tag -F MOODLE_XX_MERGED version.php''' | # '''cvs tag -F MOODLE_XX_MERGED version.php''' | ||
Revision as of 03:16, 21 July 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 -FR 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.
- Update filters (like Moodle 1.8.x bugs) in the tracker to include new unreleased versions
- Make sure the Release Notes page is updated
- Add new version on the Release page
- Update the version.php in CVS to be X.X.Y+
- cvs tag -F MOODLE_XX_MERGED version.php
