Update creation of deprecation epic to reflect updated policy

Also, update sample issues to clone for the next release.

general/development/process/release/index.md

@@ -167,17 +167,17 @@ Usually on Monday
 | 4. | ✓ | ✓ | Add all security advisories to [Security news](http://moodle.org/security) and [release notes](https://docs.moodle.org/dev/:Category:Release_notes) with links to security advisories | |Security Officer |
 | 5. | ✓ | ✓ | Notify about publications of CVE using form: https://cveform.mitre.org/ | Security Officer |
 | 6. | ✓ |  | Upgrade moodle.org and all other Moodle community sites (next sites first, then production) |  |
-| 7. | &#10003; |  | **Deprecations:**<ul><li>Create the next deprecation epic (for `X.Y+1+2y`) similar to [MDL-78075](https://tracker.moodle.org/browse/MDL-78075) and add standard issues to it:<ul><li>Final deprecation of `lib/deprecatedlib.php` (like [MDL-78076](https://tracker.moodle.org/browse/MDL-78076))</li><li>Removal of deprecated Behat steps (like [MDL-78077](https://tracker.moodle.org/browse/MDL-78077))</li><li>Removal of strings (like [MDL-78078](https://tracker.moodle.org/browse/MDL-78078)) and</li><li>Removal of renamed classes ([MDL-78079](https://tracker.moodle.org/browse/MDL-78079)).</li></ul></li></ul>The issue can be based/cloned on the previous one and linked ("has to be done after") with it.<ul><li>Review [how previous deprecation epics are going](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20text%20~%20%22Collect%20together%20deprecated%20and%20planned%20code%20changes%20for%20Moodle%22%20AND%20affectedVersion%20in%20(releasedVersions()%2C%20%22Future%20Dev%22)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuekey%20%20DESC) and share about them.</li></ul><br/>**Libraries:**<ul><li>Create the next third party libraries epic for `X.Y+1`, similar to [MDL-78024](https://tracker.moodle.org/browse/MDL-78024). The issue should refer to the list of [Moodle libraries credits](../../../community/credits/thirdpartylibs.md). The issue can be based/cloned on the previous one and linked ("has to be done after") with it. **Drag/link opened issues from the previous one**, avoiding leaving unfinished stuff.</li><li>Review [how previous library review epics are going](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20(summary%20~%20%22Review%20third%20party%20libraries%20for%20new%20versions%22%20OR%20summary%20~%20%22Review%20third-party%20libraries%20for%20upgrade%22)%20AND%20affectedVersion%20in%20(releasedVersions()%2C%20%22Future%20Dev%22)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuekey%20%20DESC) and share about them.</li></ul> | Integration Team |
+| 7. | &#10003; |  | **Deprecations:**<ul><li>If not yet present, create the deprecation epic for the next series (`X+1.0`) similar to [MDL-79719](https://tracker.moodle.org/browse/MDL-79719). The issue can be based/cloned from the previous deprecation epic and linked ("has to be done after") with it.</li><li>Add standard issues to it:<ul><li>Final deprecation of `lib/deprecatedlib.php` (like [MDL-79720](https://tracker.moodle.org/browse/MDL-79720))</li><li>Removal of deprecated Behat steps (like [MDL-79721](https://tracker.moodle.org/browse/MDL-79721))</li><li>Removal of strings (like [MDL-78078](https://tracker.moodle.org/browse/MDL-79722)) and</li><li>Removal of renamed classes ([MDL-79723](https://tracker.moodle.org/browse/MDL-79723)).</li></ul></li><li>Review [how previous deprecation epics are going](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20text%20~%20%22Collect%20together%20deprecated%20and%20planned%20code%20changes%20for%20Moodle%22%20AND%20affectedVersion%20in%20(releasedVersions()%2C%20%22Future%20Dev%22)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuekey%20%20DESC) and share about them.</li></ul><br/>**Libraries:**<ul><li>Create the next third party libraries epic for `X.Y+1`, similar to [MDL-81653](https://tracker.moodle.org/browse/MDL-81653). The issue should refer to the list of [Moodle libraries credits](../../../community/credits/thirdpartylibs.md). The issue can be based/cloned on the previous one and linked ("has to be done after") with it. **Drag/link opened issues from the previous one**, avoiding leaving unfinished stuff.</li><li>Review [how previous library review epics are going](https://tracker.moodle.org/issues/?jql=project%20%3D%20MDL%20AND%20(summary%20~%20%22Review%20third%20party%20libraries%20for%20new%20versions%22%20OR%20summary%20~%20%22Review%20third-party%20libraries%20for%20upgrade%22)%20AND%20affectedVersion%20in%20(releasedVersions()%2C%20%22Future%20Dev%22)%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20issuekey%20%20DESC) and share about them.</li></ul> | Integration Team |
 
 ## 2 weeks after
 
 | # | Major | Minor | Task | Responsibility |
 | :---: | :---: | :---: | --- | --- |
 | 1. | &#10003; |  | Once the "On Sync" period ends:<ul><li>Confirm that versions (`XY_STABLE` and `main`) diverged properly the last on-sync week. If not, proceed to it by manually bumping `main` the version to the current date @ integration.git.</li><li>Disable the ["Manage queues on continuous"](https://ci.moodle.org/view/Tracker/job/TR%20-%20Manage%20queues%20on%20continuous/) job. It has served us well.</li><li>The `integration_held` label will be removed from all [issues awaiting integration](https://tracker.moodle.org/issues/?filter=13669) and [issues awaiting component leads review](https://tracker.moodle.org/issues/?filter=23331), so they will, automatically (see next point), be moved to the various integration queues. Send an `unholding + rebase` message to all those issues.</li><li>Enable the ["Manage queues on normal"](https://ci.moodle.org/view/Tracker/job/TR%20-%20Manage%20queues%20on%20normal/) job. It will control the queues over the coming months, until the next freeze.</li><li>In the [Jenkins CI server](https://ci.moodle.org/) enable all the jobs corresponding to the new branch (`B-XYZ` view) that were created on packaging day.</li></ul> | Integration Team |
-| 2. | &#10003; |  | The discussion about environmental requirements for next X.Y+1 major release ([MDL-76724](https://tracker.moodle.org/browse/MDL-76724)) will end and the issue will be resolved **immediately**. A new issue, about the requirements for the next `X.Y+2` major release will be created at the same time by cloning the previous one and dragging any non-resolved detail (due date = 3w after release). | Integration Team |
+| 2. | &#10003; |  | The discussion about environmental requirements for next X.Y+1 major release ([MDL-79809](https://tracker.moodle.org/browse/MDL-79809)) will end and the issue will be resolved **immediately**. A new issue, about the requirements for the next `X.Y+2` major release will be created at the same time by cloning the previous one and dragging any non-resolved detail (due date = 3w after release). | Integration Team |
 | 3. | &#10003; |  | Ensure [Language pack for `main` (X.Y+1)](https://download.moodle.org/langpack/X.Y+1/) is available and merge the pull request MR4 for stop skipping the language upgrade in [moodle-ci-runner](https://github.com/moodlehq/moodle-ci-runner) repository. | Integration Team |
 | 4. | &#10003; |  | Ensure release retrospectives are held for each of the LMS teams and results are actioned. | Platform Manager / Head of educational solutions |
-| 5. | &#10003; |  | <p>Prepare for the next version of PHP.</p> <p>We need to ensure that the Moodle versions that will support the next version of PHP are compatible with it.</p> <ul><li>If an epic has not been created yet, create an epic issue for it (see [MDL-76405](https://tracker.moodle.org/browse/MDL-76405) as an example)</li> <li>Go through the list of changes for the upcoming PHP version, identify potential breaking changes in Moodle and add them to the epic.</li></ul> <p>Related links:</p> <ul><li>[PHP versions](https://www.php.net/supported-versions.php)</li> <li>[PHP.Watch](https://php.watch/versions)</li> </ul> | Integration team |
+| 5. | &#10003; |  | <p>Prepare for the next version of PHP.</p> <p>We need to ensure that the Moodle versions that will support the next version of PHP are compatible with it.</p> <ul><li>If an epic has not been created yet, create an epic issue for it (see [MDL-80117](https://tracker.moodle.org/browse/MDL-80117) as an example)</li> <li>Go through the list of changes for the upcoming PHP version, identify potential breaking changes in Moodle and add them to the epic.</li></ul> <p>Related links:</p> <ul><li>[PHP versions](https://www.php.net/supported-versions.php)</li> <li>[PHP.Watch](https://php.watch/versions)</li> </ul> | Integration team |
 | 6. | &#10003; |  | Create a fork in Developer documentation for the major release. | Integration Team |
 
 ## 1 month after