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 (link edits)
Line 1: Line 1:
The standard procedures for making Moodle releases.
This page describes the standard procedures for making Moodle releases.


===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===
Line 6: Line 6:
# Notify Moodle developers and Moodle Partners about the upcoming release
# Notify Moodle developers and Moodle Partners about the upcoming release
# Freeze stable development
# Freeze stable development
# Review and complete the Release Notes page of the upcoming version.
# Review and complete the [[:Category:Release notes|release notes]] of the upcoming version.
# Test / QA / etc
# [[Development:Weekly Code Review|Test / QA]] etc


Release day:
Release day:
Line 28: Line 28:
# 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'''
# Make sure the [[Release Notes]] page is updated
# Update the [[Latest release notes]] page
# Add new version on the [[Release]] page.
# Add new version on the [[Moodle version history]] page
# Notify all registered sys admins
# Notify all registered sys admins
# Create a new ('''blocker serious security issue!''') 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-20840 (for Moodle 1.9.7).
# Create a new ('''blocker serious security issue!''') 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-20840 (for Moodle 1.9.7).
Line 37: Line 37:


# Add all security advisories to [http://moodle.org/security Security news]
# Add all security advisories to [http://moodle.org/security Security news]
# Add all security issues to the [[Release Notes]] page with links to security advisories.
# Add all security issues to the [[:Category:Release notes|release notes]] with links to security advisories.
# Post about the release on [http://moodle.org Moodle.org] front page
# Post about the release in the [http://moodle.org/news/ moodle.org news]
# Create one new release notes page for the next version XX.Y+1 (here you can find [[Development:Release notes template|one template for that]])
# Create a new release notes page for the next version XX.Y+1 (here you can find [[Development:Release notes template|one template for that]])


===For a major release XX===
===For a major release XX===

Revision as of 11:44, 26 November 2009

This page describes 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. Review and complete the release notes of the upcoming version.
  4. 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. Update the Latest release notes page
  18. Add new version on the Moodle version history page
  19. Notify all registered sys admins
  20. Create a new (blocker serious security issue!) 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-20840 (for Moodle 1.9.7).
  21. Create a new (blocker serious security issue!) task in the Tracker "Prepare security advisories for XX.Y+1 and friends" to define/edit/polish the security advisories in the next release. Link it with the previous one as "will be resolved by". An example is MDL-20722 (for Moodle 1.9.7).

One week later:

  1. Add all security advisories to Security news
  2. Add all security issues to the release notes with links to security advisories.
  3. Post about the release in the moodle.org news
  4. Create a new release notes page for the next version XX.Y+1 (here you can find one template for that)

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=65893"
Powered by MediaWiki