From ff7bbe3f0a03c07d2b8196e570f88abc2b2cb371 Mon Sep 17 00:00:00 2001 From: Abhijeet Kasurde Date: Thu, 24 Jun 2021 02:39:04 +0530 Subject: [PATCH] [bp-2.11] Syntax fixes for docs (#75088) (cherry picked from commit 3a8fc2d2be9062d4efb152be8c0c7fb6918fc587) Co-authored-by: Chandler Swift --- docs/docsite/rst/community/development_process.rst | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/docsite/rst/community/development_process.rst b/docs/docsite/rst/community/development_process.rst index 9ca0044863f..c227218d0e5 100644 --- a/docs/docsite/rst/community/development_process.rst +++ b/docs/docsite/rst/community/development_process.rst @@ -154,10 +154,11 @@ You do not need a changelog fragment for PRs that: More precisely: + * Every bugfix PR must have a changelog fragment. The only exception are fixes to a change that has not yet been included in a release. * Every feature PR must have a changelog fragment. * New modules and plugins (except jinja2 filter and test plugins) must have ``versions_added`` set correctly, and do not need a changelog fragment. The tooling detects new modules and plugins by their ``versions_added`` value and announces them in the next release's changelog automatically. -* New jinja2 filter and test plugins, and also new roles and playbooks (for collections) must have a changelog fragment. See :ref:`changelogs_how_to_format_j2_roles_playbooks` or the `antsibull-changelog documentation for such changelog fragments _` for information on how the fragments should look like. +* New jinja2 filter and test plugins, and also new roles and playbooks (for collections) must have a changelog fragment. See :ref:`changelogs_how_to_format_j2_roles_playbooks` or the `antsibull-changelog documentation for such changelog fragments `_ for information on how the fragments should look like. We build short summary changelogs for minor releases as well as for major releases. If you backport a bugfix, include a changelog fragment with the backport PR.