diff --git a/general/development/process/release/index.md b/general/development/process/release/index.md
index 9e88da4072..135ddde9db 100644
--- a/general/development/process/release/index.md
+++ b/general/development/process/release/index.md
@@ -124,7 +124,7 @@ This should happen immediately before the next integration cycle begins on Monda
| 6. | ✓ | | In the [performance comparison repository](https://github.com/moodlehq/moodle-performance-comparison), set the new release commit hash as `$basecommit` in the master branch and create a new `MOODLE_XY_STABLE` branch from it. ([example](https://github.com/moodlehq/moodle-performance-comparison/commit/7c875f03e52641f69674235a8947131d77691299)). Also, apply it to the current performance testing infrastructure. | Integration Team |
| 7. | ✓ | ✓ | Wait for the automated (every 2 hours) moodle-package to finish building for all versions. Verify the process has ended successfully (email). | Integration Team |
| 8. | ✓ | | - Create new windows packager script (cloning the current master one and configuring it).
- Edit the stats.php script (in the `moodle-local_downloadmoodleorg` repository), adding the new branch to the versions. Push it. Next time the plugin is deployed (normally 1 week after release approx) the stats will start showing the new branch statistics.
| Integration Team |
-| 9. | ✓ | ✓ | In the Tracker: - Visit the versions page and make the release, bumping all remaining open bugs to the next point release. If there is not next (end of support), clean that version from all the issues having it as "Fix for". This must be done both for the [Moodle Project](http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011) and the [Plugins project](http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033).
- Archive all versions but the ones being released, verifying that [there aren't open issues using that version](https://tracker.moodle.org/issues/?jql=project%3DMDL%20AND%20status%20!%3D%20Closed%20AND%20fixVersion%20%3D%20VERSION_TO_ARCHIVE).
- Remove from all screens the custom fields belonging to 100% unsupported branches.
For major releases only:- Release and archive the [`Must fix for X.Y` versions](https://tracker.moodle.org/issues/?jql=affectedVersion%20~%20%22must%20fix%20for*%22%20OR%20fixVersion%20~%20%22must%20fix%20for*%22), it must be empty to do so.
| Integration Team |
+| 9. | ✓ | ✓ | In the Tracker: - Visit the versions page and make the release, bumping all remaining open bugs to the next point release. If there is not next (end of support), clean that version from all the issues having it as "Fix for". This must be done both for the [Moodle Project](http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10011) and the [Plugins project](http://tracker.moodle.org/secure/project/ViewProject.jspa?pid=10033).
- Archive all versions but the ones being released, verifying that [there aren't open issues using that version](https://tracker.moodle.org/issues/?jql=project%3DMDL%20AND%20status%20!%3D%20Closed%20AND%20fixVersion%20%3D%20VERSION_TO_ARCHIVE).
- Remove from all screens the custom fields (`Pull X.Y Branch` and `Pull X.Y Diff URL`) belonging to 100% unsupported branches and, finally, proceed to delete the fields themselves.
For major releases only:- Release and archive the [`Must fix for X.Y` versions](https://tracker.moodle.org/issues/?jql=affectedVersion%20~%20%22must%20fix%20for*%22%20OR%20fixVersion%20~%20%22must%20fix%20for*%22), it must be empty to do so.
| Integration Team |
| 10. | ✓ | |- 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). Order them properly on each screen. Re-index Tracker.
- In the CI server edit the following jobs to make them meet the new `Pull X.Y Branch` field:
- [`Bulk pre-check issues`](http://integration.moodle.org/view/tracker/job/Tracker%20-%20CI%20-%20Bulk%20precheck%20issues/)
- [`Pre-launch DEV jobs (awaiting_integration)`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Bulk%20pre-launch%20DEV%20jobs%20(awaiting_integration)/)
- [`Pre-launch DEV jobs (awaiting_clr)`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Bulk%20pre-launch%20DEV%20jobs%20(awaiting_clr)/)
- [`Pre-launch DEV jobs (list_of_mdls)`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Bulk%20pre-launch%20DEV%20jobs%20(list_of_mdls)/)
- [`Pre-launch SDEV jobs (list_of_mdls)`](https://ci.moodle.org/view/Tracker/job/STR%20-%20Bulk%20pre-launch%20SDEV%20jobs%20(list_of_mdls)/)
At the same time, remove from those jobs any branch belonging to 100% unsupported branches. - Edit the [`Tracker - CI - Check marked as integrated`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Check%20marked%20as%20integrated/) job to configure the development branches (`devbranches`) (39, 310, 311, 400...) actually active. Normally only the branch corresponding to master, but also accepts a comma separated list when under parallel development ("310,400" or "311,400" for example). Ordered by planned release date.
- Check/configure (again, this may be has been already executed few steps above) the `05. Check version.php files` jobs both for the involved branches (`XY` and `master`) to define the interval of versions allowed in each.
| Integration Team |
| 11. | ✓ | ✓ | In the Tracker:
For major releases only:- Create the new "X.Y regressions" version to be applied to every issue found to be a recent problem introduced by the major release. These issues should get priority after release.
- Adjust the [Latest regressions](https://tracker.moodle.org/issues/?filter=17528) filter (requires login).
For all releases:- Verify how the [`X.Y regressions` versions are going](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20resolution%20%3D%20Unresolved%20AND%20affectedVersion%20in%20(versionMatches(%22.*regressions%22))) (requires login) and ping Development Managers about. Package and archive them once empty.
| Integration Team |
| 12. | ✓ | | Clone [MDL-78001](https://tracker.moodle.org/browse/MDL-78001) and [MDL-78000](https://tracker.moodle.org/browse/MDL-78000), to be resolved ASAP. | Integration Team |