Note: You are currently viewing documentation for Moodle 3.7. Up-to-date documentation for the latest stable version of Moodle may be available here: Release process.

Development:Release process: Difference between revisions

From MoodleDocs
m (adding info to release also windows downloads)
Line 24: Line 24:
# Run moodle-makewindowspackages so all the windows packages will be rebuilt
# Run moodle-makewindowspackages so all the windows packages will be rebuilt
# Edit download windows/index.php page with new release info (always keeping the "+")
# Edit download windows/index.php page with new release info (always keeping the "+")
# 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. This must be done both for the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011 Moodle Project] and the [http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033 Non-core contributed modules project].
# 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 23:18, 25 October 2009

The standard procedures for making Moodle releases.

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

One week before:

  1. Notify Moodle developers and Moodle Partners about the upcoming release
  2. Freeze stable development
  3. Test / QA / etc

Release day:

  1. cvs -q update -dP
  2. Make sure all the Unit tests pass!
  3. Edit version.php, update name and version to new point release and commit
  4. cvs tag -F MOODLE_XX_MERGED version.php
  5. cvs tag -FR MOODLE_XXY to tag everything in the release
  6. cvs tag -FR MOODLE_XX_WEEKLY to make the weekly version match the release
  7. cvs -q update -dP all code on download server
  8. Run moodle-makenightlystableXX
  9. Go to download/stableXX
  10. 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
  11. Edit download index.php page with new release info and links
  12. Run moodle-makewindowspackages so all the windows packages will be rebuilt
  13. Edit download windows/index.php page with new release info (always keeping the "+")
  14. Visit releases page on tracker and make the release, bumping all remaining open bugs to the next point release. This must be done both for the Moodle Project and the Non-core contributed modules project.
  15. Update the version.php in CVS to be X.X.Y+
  16. cvs tag -F MOODLE_XX_MERGED version.php
  17. Make sure the Release Notes page is updated
  18. Add new version on the Release page
  19. Notify all registered sys admins
  20. Create a new META bug in the Tracker "META: Moodle XX.Y+1 and friends security bugs" to associate new/pending security bugs that will be fixed in the next release as subtasks. An example is MDL-19512 (for Moodle 1.9.6).

One week later:

  1. Add all security notices to Security news
  2. Add all security notices to the Release Notes page
  3. Post about the release on Moodle.org front page

For a major release XX

  1. To be documented

See also

Retrieved from "https://docs.moodle.org/37/en/index.php?title=Development:Release_process&oldid=64665"
Powered by MediaWiki