From d94114ee84bf9cd83abaae8f6ac1c918fb7733af Mon Sep 17 00:00:00 2001 From: RetroEdit Date: Sat, 27 Jun 2026 14:25:04 +0000 Subject: [PATCH] docs: fix malformed list --- doc/en/backwards-compatibility.rst | 1 + 1 file changed, 1 insertion(+) diff --git a/doc/en/backwards-compatibility.rst b/doc/en/backwards-compatibility.rst index a7ee2253d67..7c5592b0b96 100644 --- a/doc/en/backwards-compatibility.rst +++ b/doc/en/backwards-compatibility.rst @@ -45,6 +45,7 @@ c) True breakage should only be considered when a normal transition is unreasona After a reasonable amount of time the PR can be merged to base a new major release. For the PR to mature from POC to acceptance, it must contain: + * Setup of deprecation errors/warnings that help users fix and port their code. If it is possible to introduce a deprecation period under the current series, before the true breakage, it should be introduced in a separate PR and be part of the current release stream. * Detailed description of the rationale and examples on how to port code in ``doc/en/deprecations.rst``.