From a6615ef24aba0f7307ac3e6bfb15aa98bc75f80e Mon Sep 17 00:00:00 2001
From: Virgile Prevosto <virgile.prevosto@m4x.org>
Date: Tue, 19 Oct 2021 16:57:16 +0200
Subject: [PATCH] [relman] old bts is no more, and neither is frama-c-commits

---
 doc/release/branch.tex | 12 ++++++------
 1 file changed, 6 insertions(+), 6 deletions(-)

diff --git a/doc/release/branch.tex b/doc/release/branch.tex
index 8e12c44b0dc..7d8d97fc6fc 100644
--- a/doc/release/branch.tex
+++ b/doc/release/branch.tex
@@ -49,20 +49,20 @@ allowed to push/merge).
 
 \section{Creating the milestones}
 
-Create the milestones for the next release on \textsf{Mantis}
-\expertise{Julien} and \textsf{Gitlab}
-\expertise{François, Julien}
+Create the milestone for the next release on \textsf{Gitlab},
+in the Frama-C group
+\expertise{François, Julien}.
 
 
 \section{BTS}
 
-Check both \textsf{BTS}. All issues should have been at least acknowledged:  no more issues with status 'New' or only 'Assigned' should remain.
+Check public issue tracker at \href{https://git.frama-c.com/pub/frama-c/issues/} All issues should have been at least acknowledged: at least they should be assigned to someone, preferably tagged appropriately.
 
-Send a mail on the frama-c-commits mailing list: each user/developer should have a
+Send a message to the Frama-C channel on LSL's Mattermost.
+each developer should have a
 look at their own assigned/monitored/reported issues. Depending on their severity,
 the issues should be tagged with the current release, or with the next one.
 
-
 \section{Changelog}
 
 Create headers in the Changelog(s). This is to avoid some merge conflicts,
-- 
GitLab