Development:Release process: Difference between revisions
From MoodleDocs
| Line 3: | Line 3: | ||
===For a stable release on an existing branch XX with point value Y=== | ===For a stable release on an existing branch XX with point value Y=== | ||
One week before: | |||
# Notify Moodle Partners in advance about the release | |||
# Notify Moodle developers about the upcoming release | |||
# Freeze stable development | |||
# Test / QA / etc | # Test / QA / etc | ||
Release day: | |||
# '''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 | ||
| Line 22: | Line 28: | ||
# Make sure the [[Release Notes]] page is updated | # Make sure the [[Release Notes]] page is updated | ||
# Add new version on the [[Release]] page | # Add new version on the [[Release]] page | ||
# Notify | # Notify all registered sys admins | ||
One week later: | |||
# Add all security notices to [http://moodle.org/security Security news] | # Add all security notices to [http://moodle.org/security Security news] | ||
# Post about the release on [http://moodle.org Moodle.org] front page | # Post about the release on [http://moodle.org Moodle.org] front page | ||
Revision as of 00:48, 29 January 2009
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:
- Notify Moodle Partners in advance about the release
- Notify Moodle developers 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
- 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.
- 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
- Post about the release on Moodle.org front page
