summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRan Benita <ran234@gmail.com>2014-10-18 13:31:32 +0300
committerRan Benita <ran234@gmail.com>2014-10-18 13:31:32 +0300
commit8bf1e193fc0a8a62760c641ceb02f5e023980118 (patch)
treef87fd18b584b10c6081779612964b9912010df46
parentf774f819d6d406bf859d22d447895b0bc256297a (diff)
downloadxorg-lib-libxkbcommon-8bf1e193fc0a8a62760c641ceb02f5e023980118.tar.gz
README: remove section on API stability
This was useful when we *weren't* stable. But now that we are this should be obvious. Signed-off-by: Ran Benita <ran234@gmail.com>
-rw-r--r--README.md8
1 files changed, 0 insertions, 8 deletions
diff --git a/README.md b/README.md
index 2627a32..b45a674 100644
--- a/README.md
+++ b/README.md
@@ -30,14 +30,6 @@ expose fewer internal details to clients. The supported API is available
in the xkbcommon/xkbcommon-*.h files. Additional support is provided for
X11 (XCB) clients, in the xkbcommon-x11 library, xkbcommon/xkbcommon-x11.h.
-The xkbcommon API and ABI are stable. We will attempt to not break ABI during
-a minor release series, so applications written against 0.1.0 should be
-completely compatible with 0.5.3, but not necessarily with 1.0.0. However, new
-symbols may be introduced in any release. Thus, anyone packaging xkbcommon
-should make sure any package depending on it depends on a release greater than
-or equal to the version it was built against (or earlier, if it doesn't use
-any newly-introduced symbols), but less than the next major release.
-
## Relation to X11
Relative to the XKB 1.1 specification implemented in current X servers,