You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: doc/en/backwards-compatibility.rst
+1Lines changed: 1 addition & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -45,6 +45,7 @@ c) True breakage should only be considered when a normal transition is unreasona
45
45
After a reasonable amount of time the PR can be merged to base a new major release.
46
46
47
47
For the PR to mature from POC to acceptance, it must contain:
48
+
48
49
* 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.
49
50
* Detailed description of the rationale and examples on how to port code in ``doc/en/deprecations.rst``.
0 commit comments