Note:

If you want to create a new page for developers, you should create it on the Moodle Developer Resource site.

Archive release process

From MoodleDocs
Revision as of 05:42, 11 July 2008 by Martin Dougiamas (talk | contribs) (New page: 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...)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Some notes on the release process, to be fleshed out.

For a stable release on an existing branch XX with point value Y

  1. Test / QA / etc
  2. Edit version.php, update name and version to new point release and commit
  3. cvs tag -F MOODLE_XXY version.php
  4. cvs tag -F MOODLE_XX_MERGED version.php
  5. cvs -q update -dP all code on download server
  6. Run moodle-makenightlystableXX
  7. Go to download/stableXX
  8. Copy current daily as release package:
    1. cp moodle-latest-XX.zip moodle-X.X.Y.zip
    2. cp moodle-latest-XX.tgz moodle-X.X.Y.tgz
  9. Edit download index.php page with new release info and links
  10. Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release.
  11. Make sure the release notes page is updated Release