Skip to content

docs: add about removal of deprecated functionality #7021

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
kenjis wants to merge 1 commit into from
Closed

docs: add about removal of deprecated functionality #7021

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 6 additions & 1 deletion user_guide_src/source/installation/backward_compatibility_notes.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,12 @@ We try to develop our products to be as backward compatible (BC) as possible.
Only major releases (such as 4.0, 5.0 etc.) are allowed to break backward compatibility.
Minor releases (such as 4.2, 4.3 etc.) may introduce new features, but must do so without breaking the existing API.

However, the code is not mature and bug fixes may break compatibility in minor releases, or even in patch releases (such as 4.2.5). In that case, all the breaking changes are described in the :doc:`../changelogs/index`.
However, the code is not mature and bug fixes may break compatibility in **minor** releases, or even in **patch** releases (such as 4.2.5).

Deprecated functionality may be removed in the next **minor** version or later.
Please discontinue use as soon as possible.

In any case, all the breaking changes are described in the :doc:`../changelogs/index`.

*****************************
What are not Breaking Changes
Expand Down