Lines Matching refs:compatibility

19 API compatibility in the `master` branch across minor version changes (e.g.
21 compatibility on major version changes (e.g. from 3.x to 4.0). We also maintain
22 ABI compatibility within LTS branches; see the next section for details.
26 We maintain API compatibility in released versions of Mbed TLS. If you have
34 not considered API compatibility breaks:
47 There are rare exceptions where we break API compatibility: code that was
50 comes in conflict with backwards compatibility, we will put security first,
51 but always attempt to provide a compatibility option.
56 compatibility (same definition as API except with re-linking instead of
60 will put security first but provide a compatibility option. (So far we never
61 had to break ABI compatibility in an LTS branch, but we occasionally had to
65 CONTRIBUTING](CONTRIBUTING.md#backwards-compatibility).