Note: You are currently viewing documentation for Moodle 1.9. Up-to-date documentation for the latest stable version is available here: Release process.

Development:Release process: Difference between revisions

From MoodleDocs
Line 10: Line 10:


Release day:
Release day:
# '''cvs -q update -dP'''
# Make sure all the Unit tests pass!
# Make sure all the Unit tests pass!
# 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 in the integration repository
# '''cvs tag -F MOODLE_XX_MERGED version.php'''
# push change to main git repo, github and Gitorious
# sync CVS mirror
# '''cvs tag -FR MOODLE_XXY''' to tag everything in the release
# '''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 tag -FR MOODLE_XX_WEEKLY''' to make the weekly version match the release
Line 26: Line 26:
# 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. 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].
# 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+
# '''cvs tag -F MOODLE_XX_MERGED version.php'''
# Add the release date to the [[:Category:Release notes|release notes]]
# Add the release date to the [[:Category:Release notes|release notes]]
# Update the [[Latest release notes]] page
# Update the [[Latest release notes]] page
Line 37: Line 35:


One week later:
One week later:
 
# Update the version.php in git to be X.X.Y+ during the next weekly PULL process
# 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 [[:Category:Release notes|release notes]] with links to security advisories
# Add all security issues to the [[:Category:Release notes|release notes]] with links to security advisories

Revision as of 22:27, 25 December 2010

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 and post in the General developer forum to inform everyone of the freeze
  3. Review and complete the release notes of the upcoming version.
  4. Test / QA etc

Release day:

  1. Make sure all the Unit tests pass!
  2. Edit version.php, update name and version to new point release and commit in the integration repository
  3. push change to main git repo, github and Gitorious
  4. sync CVS mirror
  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. Add the release date to the release notes
  16. Update the Latest release notes page
  17. Add the new version to the Moodle version history page
  18. Include the new versions in Moodle 1.8 release notes and Moodle 1.9 release notes
  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. Update the version.php in git to be X.X.Y+ during the next weekly PULL process
  2. Add all security advisories to Security news
  3. Add all security issues to the release notes with links to security advisories
  4. Update the Latest Release block on Moodle.org news
  5. Post about the release in the moodle.org news
  6. Create a new release notes page for the next version XX.Y+1 (here you can find one template for that)

See also

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