summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorPhilip Withnall <philip@tecnocode.co.uk>2014-11-03 00:13:51 +0000
committerPhilip Withnall <philip@tecnocode.co.uk>2014-11-03 00:16:12 +0000
commit30cf8a58e0f7f6520112c45b7d2877bdecbd6bc1 (patch)
treec7c62c1a733fb940a8320ebf17ffe312f4e73981 /README
parent8a695555b68671a765f95603dd054046df3e8a5d (diff)
downloadlibgdata-30cf8a58e0f7f6520112c45b7d2877bdecbd6bc1.tar.gz
core: Mark all API as stable and impose API and ABI stability guarantees
It’s time for libgdata to grow up and start guaranteeing some stability for its users. In this vein, it’s already been API stable for around 3 years (since 0.9.1) — it’s about time that was made explicit. http://upstream-tracker.org/versions/libgdata.html is quite interesting.
Diffstat (limited to 'README')
-rw-r--r--README2
1 files changed, 1 insertions, 1 deletions
diff --git a/README b/README
index 93adb6a9..5354b66a 100644
--- a/README
+++ b/README
@@ -8,7 +8,7 @@ the common Google services, and has full asynchronous support.
See the test programs in gdata/tests/ for simple examples of how to use the
code.
-libgdata's API is currently unstable and is likely to change wildly.
+libgdata is API and ABI stable.
Dependencies
============