API: Update main description to reflect reality
authorKunal Mehta <legoktm@member.fsf.org>
Wed, 28 Feb 2018 04:36:34 +0000 (20:36 -0800)
committerKunal Mehta <legoktm@member.fsf.org>
Wed, 28 Feb 2018 04:45:58 +0000 (20:45 -0800)
commitc9b3612baf6872c699c4abc400fc2813d4df5ff1
tree4b03b5171dc0392dfc6afaa938a0fad708f7e317
parent4d9dbc7d8d4a6a739d48a3ee4888f7ef3f85763c
API: Update main description to reflect reality

For quite a while now, the API no longer "may change at any time". Any
potential breaking change goes through code review, usage analysis, and
usually, a deprecation process.

This process was implemented as part of the "API roadmap"[1] RfC in
2014.

Today, the API is mature and stable, but still actively developed and
maintained. Breaking changes can still happen, and we want people to
subscribe to the -announce mailing list, but it's not as scary as the
old text implied.

[1]
<https://www.mediawiki.org/wiki/Requests_for_comment/API_roadmap#Deprecation_process>

Change-Id: If13172a35a3d041bce745aa72a835bfddcfe62c0
includes/api/i18n/en.json