#
|
Major
|
Minor
|
Task
|
Responsibility
|
1.
|
✓
|
|
Make sure there are no real blockers introduced in the last weekly (install / upgrade ...)
|
Integration Lead
|
2.
|
✓
|
|
Verify all unit tests, QA tests and integration tests have passed.
|
Integration Lead
|
3.
|
✓
|
|
Run the mdlrelease process, with the special steps for a Major release.
- Edit version.php, update release and version to new release values and commit in the integration repository.
- Tag the integration repository with a tag name vX.Y.0 using "MOODLE_XY" as a tag message.
- Create the new MOODLE_XY_STABLE branch.
- Move master to next X.Y+1 version.
- Update the CI server(s) by cloning all the "master" jobs to a new "MXY" view. Adjust "master" compare DB jobs to check for upgrade from MOODLE_XY_STABLE.
- Push changes to the main Git repo, Github and Gitorious.
|
Integration Lead
|
4.
|
✓
|
|
Wait for the automated moodle-package to finish building for all versions. Verify the process has ended successfuly (email).
|
Integration Lead
|
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 "+").
- Create new windows packager script (cloning the current master one and configuring it).
- Copy the xampp_version_head.php file to xampp_version_XY.php.
- Create new windows_wpiXY dir by cloning the previous one (HEAD based), configuring build-latest-XY.sh.
- Edit the stats script, adding the new branch to the versions.
|
Integration Lead
|
6.
|
✓
|
|
In the Tracker:
- Visit the 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 Add-ons project. Archive every released version > 6 months old.
- Create the new "Pull X.Y Branch" and "Pull X.Y Diff URL" custom fields and spread them to all the screens needing them (copy from previous ones). Reindex Tracker. Order them properly on each screen. Hide from all screens the custom fields belonging to 100% unsupported branches.
|
Integration Lead
|
7.
|
✓
|
|
Add/update the release date, build number and link on the Releases page.
|
Integration Lead
|
8.
|
✓
|
|
Post a "git repos updated & tagged" message on the Partner forum
|
Integration Lead
|