Archive release process

Warning: This page is no longer in use. The information contained on the page should NOT be seen as relevant or reliable.

Please see the Combined release process page.

For a stable release on an existing branch XY with point value Z (eg. X.Y.Z)

One week before

1. Notify Moodle developers and Moodle Partners about the upcoming release
   • Ask the AMOS maintainer to merge fixes from en_fix pack and then integrate them.
2. Identify security issues that need to be integrated.
   • Integrate from provided patches into supported branches (including branches supported only for security issues).
   • Ensure security issues are given priority in weekly integration and testing.
   • Collect security issues into a clone of MDL-39530 to prepare for release of Security Advisories.
3. Freeze stable development and post in the General developer forum to inform everyone of the freeze
4. Review and complete the release notes of the upcoming version using the template
   • Ensure all issues labelled with "ui_change" or "api_change" are listed as functional or API changes respectively in the release notes.
5. Begin preparing the security advisories to be sent on release day.
6. Test / QA etc.

During the week prior release

1. Normal integration / testing / upstream / weekly cycle. It will constitute, somehow, the "release candidate" to be packaged and released.
2. Determine which security issues will be integrated.
   • Request CVE Identifiers by emailing issue descriptions to distros@vs.openwall.org with a message like... The following security issues have been discovered in Moodle. We request CVE Identifiers for these issues. We will be releasing the security announcements for these on moodle.org on XXX at 12noon AWST which is 04:00 UTC. The email subject should include the characters [vs]. The format needs to be plain text or encrypted. When granted CVE Identifiers, our issues should appear in the CVE list. More instructions are available.
3. Create the next X.Y.Z+1 versions in the Tracker (both for the Moodle Project and the Non-core contributed modules project).

Packaging day

This should happen immediately before the next integration cycle begins on Monday (i.e., some days after last weekly, 2 days prior to official release).

1. Make sure there are not real blockers introduced by last weekly (install / upgrade ...)
2. Make sure all the Unit tests pass!
3. Run the mdlrelease process, that will do, for a release:
   • Edit version.php, update release and version to new point release and commit in the integration repository
   • Tag the integration repository with a tag name vX.Y.Z using "MOODLE_XYZ" as a tag message
   • push change to main git repo, github and Gitorious
4. Wait the automated moodle-package to finish building all the versions. Verify the process has ended ok (email).
5. In the download server:
   • Duplicate the download/index.php page and amend it with new release info and links
   • Duplicate the download/windows/index.php page and amend it with new release info (always keeping the "+")
6. In the Tracker:
   • 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. Archive every released version > 6mo ago.
   • Hide from all screens the custom fields belonging to 100% unsupported branches.
7. Add/update the release date, build number and link on the Releases page.
8. Post a "git repos updated & tagged" done message on the Partner forum

Release day

1. The execution of "moodle-package-extract-and-postprocess X" script may be needed if the releases *are not going to be published on Monday* but another weekday (X is the weekday, (1-7) starting in Monday).
2. Replace the download/index.php page with its updated counterpart.
3. Replace the download/windows/index.php page with its updated counterpart.
4. Notify all registered sys admins, including security notes with CVE identifiers.
5. Post about the release in the moodle.org news
6. (deprecated) Update the Latest Release block on Moodle.org news

One week after release day

1. Update the version.php in git to be X.Y.Z+ during the next weekly integration process
2. Create a new release notes page for the next version X.Y.(Z+1) (here you can find one template for that)
3. Add all security advisories to Security news and release notes with links to security advisories
4. Send a plain text email to the following email list: oss-security@lists.openwall.com An appropriate message when sending the issues is... The following security notifications have now been made public. Thanks to OSS members for their cooperation. ...followed by the security notes.

See also

• Releases
• Major release process
• Deprecation