README: Add note on upgrading between libpldm versions
This is best done successively.
Change-Id: I2d2f639d017358408fd079c51b3da259ba579536
Signed-off-by: Andrew Jeffery <andrew@codeconstruct.com.au>
diff --git a/README.md b/README.md
index 4503dab..12fe6a4 100644
--- a/README.md
+++ b/README.md
@@ -71,3 +71,12 @@
stable category. However, this may not always be possible. What to do when
required functions fall into the deprecated or testing categories is discussed
in [CONTRIBUTING](CONTRIBUTING.md#Library-background).
+
+### Upgrading libpldm
+
+libpldm is maintained with the expectation that users move between successive
+releases when upgrading. This constraint allows the library to reintroduce types
+and functions of the same name in subsequent releases in the knowledge that
+there are no remaining users of previous definitions. While strategies are
+employed to avoid breaking existing APIs unnecessarily, the library is still to
+reach maturity, and we must allow for improvements to be made in the design.