From 0a3fa828f89f3eaebcd69aa31148d773c590ae55 Mon Sep 17 00:00:00 2001 From: Donatas Abraitis Date: Sun, 13 Feb 2022 21:23:53 +0200 Subject: [PATCH] doc: An example how we do RC tagging for stabilization branch Signed-off-by: Donatas Abraitis --- doc/developer/workflow.rst | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/doc/developer/workflow.rst b/doc/developer/workflow.rst index 2005e9d8bb..45bee17b71 100644 --- a/doc/developer/workflow.rst +++ b/doc/developer/workflow.rst @@ -141,6 +141,16 @@ March/July/November. Walking backwards from this date: - 2 weeks earlier, a ``frr-X.Y-rc`` release candidate is tagged. + .. code-block:: console + + % git remote --verbose + upstream git@github.com:frrouting/frr (fetch) + upstream git@github.com:frrouting/frr (push) + + % git checkout dev/8.2 + % git tag frr-8.2-rc + % git push upstream frr-8.2-rc + - on release date, the branch is renamed to ``stable/MAJOR.MINOR``. The 2 week window between each of these events should be used to run any and -- 2.39.5