diff --git a/top/README-release b/top/README-release
index 5a8e8a59c1..8d242d04ee 100644
--- a/top/README-release
+++ b/top/README-release
@@ -19,6 +19,10 @@ Here are most of the steps we (maintainers) follow when making a release.
 
     git push origin master
 
+* Check that the GitLab autobuilder is reporting all is well:
+
+    https://gitlab.com/gsasl/gsasl/-/pipelines
+
 * Run the following command to download any new translations:
 
     ./bootstrap && ./configure
@@ -64,28 +68,6 @@ Once all the builds and tests have passed,
     v=$(cat .prev-version)
     git push origin master tag v$v
 
-* Announce it on Savannah first, so you can include the savannah.org
-  announcement link in the email message.
-
-  Go to the news-submission form:
-
-    https://savannah.gnu.org/news/submit.php?group=@PACKAGE@
-
-  If it does not work, then enable "News" for the project via this link:
-
-    https://savannah.gnu.org/project/admin/editgroupfeatures.php?group=@PACKAGE@
-
-  Write something like the following:
-
-    Subject: @PACKAGE@-X.Y released [stable]
-    +verbatim+
-    ...paste the announcement here...
-    -verbatim-
-
-  Then go here to approve it:
-
-    https://savannah.gnu.org/news/approve.php?group=@PACKAGE@
-
 * Send the announcement email message.
 
 * After each non-alpha release, run
