aboutsummaryrefslogtreecommitdiff
path: root/docs/devel
diff options
context:
space:
mode:
authorCornelia Huck <cohuck@redhat.com>2020-01-13 11:30:23 +0100
committerCornelia Huck <cohuck@redhat.com>2020-01-27 12:13:09 +0100
commit174b72aa38df8b60eb624a5c6f65126fa62bc6d6 (patch)
tree3ee9afe8c6c20b4c45f5a5ef8403c8920a700992 /docs/devel
parent596cc12ccd6c124758dee686a67287e8584b2fc7 (diff)
docs/devel: fix stable process doc formatting
Enumeration of stable criteria needs proper bullet points. Message-Id: <20200113103023.31255-1-cohuck@redhat.com> Reviewed-by: Stefan Hajnoczi <stefanha@redhat.com> Signed-off-by: Cornelia Huck <cohuck@redhat.com>
Diffstat (limited to 'docs/devel')
-rw-r--r--docs/devel/stable-process.rst6
1 files changed, 4 insertions, 2 deletions
diff --git a/docs/devel/stable-process.rst b/docs/devel/stable-process.rst
index 98736a9ea4..e541b983fa 100644
--- a/docs/devel/stable-process.rst
+++ b/docs/devel/stable-process.rst
@@ -18,8 +18,10 @@ What should go into a stable release?
-------------------------------------
Generally, the following patches are considered stable material:
-- Patches that fix severe issues, like fixes for CVEs
-- Patches that fix regressions
+
+* Patches that fix severe issues, like fixes for CVEs
+
+* Patches that fix regressions
If you think the patch would be important for users of the current release
(or for a distribution picking fixes), it is usually a good candidate