Development:Release process: Difference between revisions
From MoodleDocs
| Line 34: | Line 34: | ||
# Add all security notices to the [[Release Notes]] page | # Add all security notices to the [[Release Notes]] page | ||
# Post about the release on [http://moodle.org Moodle.org] front page | # Post about the release on [http://moodle.org Moodle.org] front page | ||
# Create new META bug in the Tracker to associate new security bugs as subtasks there (add the default "Prepare security advisories for XXX"). See MDL-19512 as example (for Moodle 1.9.6). | # Create new META bug in the Tracker to associate new/pending security bugs as subtasks there (add the default "Prepare security advisories for XXX"). See MDL-19512 as example (for Moodle 1.9.6). | ||
===For a major release XX=== | ===For a major release XX=== | ||
# To be documented | # To be documented | ||
Revision as of 18:44, 15 June 2009
The standard procedures for making Moodle releases.
For a stable release on an existing branch XX with point value Y
One week before:
- Notify Moodle developers and Moodle Partners about the upcoming release
- Freeze stable development
- Test / QA / etc
Release day:
- 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 tag -FR MOODLE_XX_WEEKLY to make the weekly version match 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 the version.php in CVS to be X.X.Y+
- cvs tag -F MOODLE_XX_MERGED version.php
- 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
- Notify all registered sys admins
One week later:
- Add all security notices to Security news
- Add all security notices to the Release Notes page
- Post about the release on Moodle.org front page
- Create new META bug in the Tracker to associate new/pending security bugs as subtasks there (add the default "Prepare security advisories for XXX"). See MDL-19512 as example (for Moodle 1.9.6).
For a major release XX
- To be documented
