diff --git a/ReleaseProcess.md b/ReleaseProcess.md
index f29c5b2..6f4ba1e 100644
--- a/ReleaseProcess.md
+++ b/ReleaseProcess.md
@@ -128,6 +128,8 @@ as well as for bug targeting. To create a new milestone:
    3.  Verify that the signature was done correctly: `gpg --verify TARBALL.asc`
     -   The AppArmor signing key has the fingerprint **3ECD CBA5 FB34 D254 961C C53F 6689 E64E 3D36 64BB**
     - [sbeattie]: **XXX** where should the signatures be uploaded / attached?
+    - [sbeattie]: followup: created a wiki page like so <https://gitlab.com/apparmor/apparmor/-/wikis/3.1.1_Signatures>
+    - **FIXME** This should be scripted.
 
 9.  \[Optional\] upload packages based on the release to the appropriate apparmor-dev ppa: https://launchpad.net/~apparmor-dev/+archive/apparmor-X.Y (where X.Y is the series version)
 10.  Create a new release from the milestone: https://launchpad.net/apparmor/+milestone/X.Y.Z/+addrelease