From 8ce15e50be8a4498b6d356c39259857e776a21f3 Mon Sep 17 00:00:00 2001 From: kenjis Date: Tue, 24 Jan 2023 11:20:32 +0900 Subject: [PATCH] docs: add about removal of deprecated Config items --- .../source/installation/backward_compatibility_notes.rst | 2 ++ 1 file changed, 2 insertions(+) diff --git a/user_guide_src/source/installation/backward_compatibility_notes.rst b/user_guide_src/source/installation/backward_compatibility_notes.rst index 65d1f9179ebd..e265d5a34968 100644 --- a/user_guide_src/source/installation/backward_compatibility_notes.rst +++ b/user_guide_src/source/installation/backward_compatibility_notes.rst @@ -13,5 +13,7 @@ However, the code is not mature and bug fixes may break compatibility in minor r What are not Breaking Changes ***************************** +- The deprecated Config items are not covered by backwards compatibility (BC) promise. It may be removed in the next + **minor** version or later. - System messages defined in **system/Language/en/** are strictly for internal framework use and are not covered by backwards compatibility (BC) promise. If developers are relying on language string output they should be checking it against the function call (``lang('...')``), not the content. - `Named arguments `_ are not covered by backwards compatibility (BC) promise. We may choose to rename method/function parameter names when necessary in order to improve the codebase.