(RELEASE.md): Log instructions to use label during release MR creation

Signed-off-by: Daniel Silverstone <dsilvers@digital-scurf.org>

1 files changed, 7 insertions, 0 deletions

diff --git a/RELEASE.md b/RELEASE.md
index 845c41b..98d6ef7 100644
--- a/RELEASE.md
+++ b/RELEASE.md
@@ -45,6 +45,8 @@ For the top crate `subplot` additionally do the following:
    successfully.
 2. Update `NEWS.md` with an end-user oriented summary of the changes
    in all crates since the previous release, if there are any.
+   Particularly check the [Fixed in next version][fixedstuff] issues
+   against the NEWS.
 3. Update `debian/changelog` with a summary of any changes to the
    Debian packaging. Use the `dch` command to edit the file to get the
    format right: `dch -v X.Y.Z-1 "New release"` to start a new
@@ -52,6 +54,11 @@ For the top crate `subplot` additionally do the following:
    and `dch -r ""` to mark the version as ready for release.
 4. Commit the changes in all crates and submit as a merge request via
    GitLab.
+   Ensure the MR contains references to close all of the
+   [Fixed in next version][fixedstuff] issues so that all the issue
+   authors get notified of the release.
+
+[fixedstuff]: https://gitlab.com/subplot/subplot/-/issues?label_name[]=fixed-in-next-version
 
 Once the above changes have been merged, make the actual release (note
 that these steps are meant to be possible to automate, later on, and