From bee3756cd4e3cb6b3da6995e7b6e53338c1bd437 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Fran=C3=A7ois=20Bobot?= <francois.bobot@cea.fr>
Date: Fri, 17 Jan 2020 16:41:33 +0100
Subject: [PATCH] [release] Updates release doc: creates branch stable/release
by using frama-ci.
---
doc/release/branch.tex | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/doc/release/branch.tex b/doc/release/branch.tex
index cee2baa5827..4dc6cb28eb7 100644
--- a/doc/release/branch.tex
+++ b/doc/release/branch.tex
@@ -22,8 +22,19 @@ $\rightarrow$ Repository $\rightarrow$ Protected Branches.
\section{Creating the branch}
Create the branch \texttt{stable/release} where \texttt{release} is the
-element name.
-
+element name using \texttt{frama-ci-create-branch} tool:
+\begin{enumerate}
+\item Install \texttt{frama-ci} tools:
+\begin{shell}
+opam pin add frama-ci-tools git@git.frama-c.com:frama-c/Frama-CI.git
+\end{shell}
+\item Create an API token for gitlab, in your gitlab profile settings
+\item Run the command
+\begin{shell}
+frama-ci-create-branch --token=\$TOKEN \
+--new-branch=stable/release --default-branch
+\end{shell}
+\end{enumerate}
What can be committed in this branch must follow the release schedule,
and go through Merge-requests. Everything else should go in \texttt{master},
which can then be reset to standard-level protection (Developers + Masters
--
GitLab