Update issues to clone for the next release

general/development/process/release/index.md

@@ -90,7 +90,7 @@ sidebar_position: 7
 | :---: | :---: | :---: | --- | --- |
 | 1. | ✓ |  | Clone as many filters as needed in the Tracker, modifying them to point to the new, upcoming, branch (keeping same perms, title...). | Integration Team |
 | 2. | ✓ | ✓ | Create new minor version X.Y.Z+1 in the Tracker (MDL and CONTRIB). Archive any version > 6 months old, 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). | Integration Team |
-| 3. | ✓ |  | Clone [MDL-77940](https://tracker.moodle.org/browse/MDL-77940) and bump all versions, requires and dependencies along all plugins in codebase to planned release dates. | Integration Team |
+| 3. | ✓ |  | Clone [MDL-81549](https://tracker.moodle.org/browse/MDL-81549) and bump all versions, requires and dependencies along all plugins in codebase to planned release dates. | Integration Team |
 | 4. | ✓ | ✓ | Post a "Heads-up" message on the [General Developer forum](http://moodle.org/mod/forum/view.php?id=55) and [MUA website](https://moodleassociation.org/). | Platform Manager |
 | 5. | ✓ | ✓ | Post a "Heads-up" message on the [Partners forum](https://partners.moodle.com/mod/forum/view.php?id=147). | Security Officer |
 | 6. | ✓ | ✓ | Post a "Heads-up" message on Twitter and other outlets. | Marketing Officer |
@@ -127,7 +127,7 @@ This should happen immediately before the next integration cycle begins on Monda
 | 9. | &#10003; | &#10003; | In the Tracker: <ul><li>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).</li><li>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).</li><li>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.</li></ul><br/>For major releases only:<ul><li>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.</li></ul> | Integration Team |
 | 10. | &#10003; |  |<ul><li>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.</li><li>In the CI server edit the following jobs to make them meet the new `Pull X.Y Branch` field:<ul><li>[`Bulk pre-check issues`](http://integration.moodle.org/view/tracker/job/Tracker%20-%20CI%20-%20Bulk%20precheck%20issues/)</li><li>[`Pre-launch DEV jobs (awaiting_integration)`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Bulk%20pre-launch%20DEV%20jobs%20(awaiting_integration)/)</li><li>[`Pre-launch DEV jobs (awaiting_clr)`](https://ci.moodle.org/view/Tracker/job/TR%20-%20Bulk%20pre-launch%20DEV%20jobs%20(awaiting_clr)/)</li><li>[`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)/)</li><li>[`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)/)</li></ul><br/>At the same time, remove from those jobs any branch belonging to 100% unsupported branches.</li><li>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 `main`, but also accepts a comma separated list when under parallel development ("310,400" or "311,400" for example). Ordered by planned release date.</li><li>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 `main`) to define the interval of versions allowed in each.</li></ul> | Integration Team |
 | 11. | &#10003; | &#10003; | In the Tracker: <br/>For major releases only:<ul><li>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.</li><li>Adjust the [Latest regressions](https://tracker.moodle.org/issues/?filter=17528) filter (requires login).</li></ul><br/>For all releases:<ul><li>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.</li></ul> | Integration Team |
-| 12. | &#10003; |  | 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 |
+| 12. | &#10003; |  | Clone [MDL-81615](https://tracker.moodle.org/browse/MDL-81615) and [MDL-81616](https://tracker.moodle.org/browse/MDL-81616), to be resolved ASAP. | Integration Team |
 | 13. | &#10003; |  | <ul><li>Create the new `MOODLE_XY_STABLE` and `lastbased-MOODLE_XY_STABLE` branches in the security repo (branching from the just created upstream `MOODLE_XY_STABLE` branch).</li><li>Cherry pick any security commit present in the security repository's `main` branch to the new `MOODLE_XY_STABLE` branch (note that normally there should not be any, see point #1 check list above).</li><li>Verify the new security jobs exist for the new branch and check it's working in all servers, keeping only enabled the public one.</li></ul> | Integration Team |
 | 14. | &#10003; |  | Protect the MOODLE_XY_STABLE branches in github interface to prevent non-FF accidents ( [MDLSITE-4183](https://tracker.moodle.org/browse/MDLSITE-4183) ) | Integration Team |