From d1c77fc9627181a2a5851d3bc6f193c2b0f66320 Mon Sep 17 00:00:00 2001
From: Jiri Kyjovsky <j1.kyjovsky@gmail.com>
Date: Fri, 16 Dec 2022 17:19:40 +0100
Subject: [PATCH] docs: document release-banner command

---
 doc/how_to_release_copr.rst | 14 ++++++++++++++
 1 file changed, 14 insertions(+)

diff --git a/doc/how_to_release_copr.rst b/doc/how_to_release_copr.rst
index 5cd0dd975..47866f331 100644
--- a/doc/how_to_release_copr.rst
+++ b/doc/how_to_release_copr.rst
@@ -10,6 +10,15 @@ good to know what's ahead.
 Keep amending this page if you find something not matching reality or expectations.
 
 
+Create warning banner about release
+-----------------------------------
+
+
+Use script in frontend's ``manage.py`` to announce an outage::
+
+    ./manage.py warning-banner --outage_time "2022-12-31 13:00-16:00 UTC" --ticket 1234
+
+
 Pre-release
 -----------
 
@@ -422,6 +431,11 @@ It is often good idea to put new (filtered) ``%changelogs`` entries there.
 Final steps
 ...........
 
+Remove the warning banner from frontend page by::
+
+    ./manage.py warning-banner --remove
+
+
 Check if the `MODIFIED bugs <https://bugzilla.redhat.com/buglist.cgi?bug_status=POST&bug_status=MODIFIED&classification=Community&list_id=4678039&product=Copr&query_format=advanced>`_
 (that are not ON_QA) are fixed in released Copr or not, move them ON_QA.