Commit 305a97f3 authored by Philip Withnall's avatar Philip Withnall
Browse files

docs: Make the API stability policy a little more mature

In reality, nothing has changed wildly, and that’s probably how the
project will continue. Things may change wildly when they land, but once
time passes after they’ve landed, they become part of the landscape and
we will be more considerate about changing them.
Signed-off-by: Philip Withnall's avatarPhilip Withnall <>
parent c761c9fd
Pipeline #131223 passed with stages
in 6 minutes and 18 seconds
......@@ -10,7 +10,10 @@ libglib-testing is a separate project from GLib itself for two reasons:
• To keep test harness API out of libglib, since it should only be needed
at test time, not at runtime.
All the library APIs are currently unstable and are likely to change wildly.
All new library APIs are unstable and have the potential to change wildly after
they’re added. After they have been used for a couple of months, they are
unlikely to change further. Consideration will be made for how widely used an
API is before potentially changing or breaking it.
Supports Markdown
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment