diff --git a/Modelica/UsersGuide/ReleaseNotes.mo b/Modelica/UsersGuide/ReleaseNotes.mo
index ac20ac0692..0e02e322ff 100644
--- a/Modelica/UsersGuide/ReleaseNotes.mo
+++ b/Modelica/UsersGuide/ReleaseNotes.mo
@@ -112,7 +112,7 @@ more of the following changes.
- Correcting an equation.
-- Correcting attributes quantity/unit/defaultUnit in a declaration.
+- Correcting attributes quantity/unit/displayUnit in a declaration.
- Improving/fixing the documentation.
- Introducing a new name in the public section of a class
(model, package, ...) or in any section of a partial class is not allowed.
@@ -122,6 +122,45 @@ more of the following changes.
class should only be done if absolutely necessary to fix a bug.
The problem is that this might be non-backward compatible,
because a user might already extend from this class and already using the same name.
+- The changes should not significantly degrade performance.
+
+
+As a recommendation, a minor version may in addition contain one or more of the following changes.
+
+
+
+- Add new classes (in partial packages this may break backwards compatibility, so in those cases only when necessary).
+- Modify Examples (including renaming).
+- Improve/fix the documentation.
+- Add new names in the public section of a class (or in any section of a partial class), even if it may break backwards compatibility, but should satisfy:
+
+- Any new input connector, or connector with annotation
mustBeConnected must be conditional and as default not enabled.
+- Any new parameter must have a default value.
+- Any new function input must be after existing inputs and have a default value.
+- Any new function output must be after existing outputs.
+- Any new enumeration member must be after existing ones.
+- Any new record members should be after existing ones, and have a default value (needed if there are any record constructor calls).
+
+
+- Delete/rename names in the protected section of a non-partial class if unlikely to be used.
+- Change visibility from public to protected if unlikely to be used.
+- The changes should not significantly degrade performance.
+
+
+Note that many of these changes may break backwards compatibility in very rare cases.
+
+
+The user perspective is that user can rely on this library to be backwards compatible for bug fix versions and practically backwards compatible for minor versions.
+Additionally, they can rely on new major versions providing conversion scripts.
+Provided you don't rely on any of the following:
+
+
+- Models that are marked as Example or documentation models.
+You can use them for inspiration and copy the Example, but directly using Example models in user models should be avoided.
+- Extending a non-partial class with named elements (either directly or indirectly by using multiple inheritance).
+- Unqualified import from the library.
+- Clear bugs in the library.
+- Equivalence between a copy of record or enumeration class and the one in the standard library.