Merge branch 'timhunt-patch-1'

general/community/meetings/2024/05.md

@@ -17,7 +17,7 @@ sidebar_position: -05
 1. [Moodle Developer Experience (DX) update](./_files/2024-05-DX-presentation.pdf)
     [Andrew Lyons](https://moodle.org/user/profile.php?id=268794) Moodle HQ
     - Changes to [Moodle Versioning and Deprecation policies](https://moodle.org/mod/forum/discuss.php?d=457946)
-    - Writing upgrade notes for Moodle 4.5 and up (MDL-81125 | [Discussion](https://moodle.org/mod/forum/discuss.php?d=457756))
+    - [Writing upgrade notes for Moodle 4.5 and up](../../../development/upgradenotes). (Added in MDL-81125 | See also [this discussion](https://moodle.org/mod/forum/discuss.php?d=457756))
     - Coding Style and [MoodleCS](../../../development/tools/phpcs.md)
     - Dependency Injections
         - Hooks

general/development/upgradenotes.md

@@ -21,7 +21,7 @@ From Moodle 4.5 a new tool, `upgradenotes` has been created to help improve upgr
 - Think about whether your change actually needs documenting in upgrade notes:
   - if your change is in a plugin then it probably does not have any public APIs
   - most bug fixes do not need to be noted unless they change an API
-- When deprecating a feature, the replacement should also be mentioned
+- When deprecating a feature, the replacement should also be mentioned. To put it another way: what developers want to know is the right way to do things in the future, so focus on explaining that.
 
 ## Using `upgradenotes`