Development:Release process: Difference between revisions
From MoodleDocs
Helen Foster (talk | contribs) (update lLatest Release block (thanks to Séverin for the reminder)) |
Helen Foster (talk | contribs) (Include the new versions in release notes pages (thanks to Séverin again for the reminder)) |
||
Line 31: | Line 31: | ||
# Update the [[Latest release notes]] page | # Update the [[Latest release notes]] page | ||
# Add the new version to the [[Moodle version history]] page | # Add the new version to the [[Moodle version history]] page | ||
# Include the new versions in [[Moodle 1.8 release notes]] and [[Moodle 1.9 release notes]] | |||
# 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). |
Revision as of 16:35, 11 February 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:
- Notify Moodle developers and Moodle Partners about the upcoming release
- Freeze stable development
- Review and complete the release notes of the upcoming version.
- Test / QA etc
Release day:
- cvs -q update -dP
- Make sure all the Unit tests pass!
- 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
- cvs tag -FR MOODLE_XX_WEEKLY to make the weekly version match the release
- 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
- Run moodle-makewindowspackages so all the windows packages will be rebuilt
- 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 Moodle Project and the 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 release notes
- Update the Latest release notes page
- Add the new version to the Moodle version history page
- Include the new versions in Moodle 1.8 release notes and Moodle 1.9 release notes
- 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!) 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:
- Add all security advisories to Security news
- Add all security issues to the release notes with links to security advisories
- Update the Latest Release block on Moodle.org news
- Post about the release in the moodle.org news
- 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
To be documented...
See also
- Development:Stable branch support
- MDLSITE-699: How to repackage one weekly at any moment (a.k.a. "emergency weekly").