Lines Matching +full:backwards +full:- +full:incompatible

5 - The [`master`](https://github.com/Mbed-TLS/mbedtls/tree/master) branch:
8 - The [`development`](https://github.com/Mbed-TLS/mbedtls/tree/development) branch:
10   prepared. It has API changes that make it incompatible with Mbed TLS 2.x,
12 - One or more long-time support (LTS) branches: these only get bug fixes and
14   [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28).
17 such as [`archive/mbedtls-2.7`](https://github.com/Mbed-TLS/mbedtls/tree/archive/mbedtls-2.7).
31 ## Backwards Compatibility for application code
35 undocumented features, then you should be able to re-compile it without
40 compile-time configuration (`mbedtls/mbedtls_config.h`) or the same modified
41 compile-time configuration. Changing compile-time configuration options can
42 result in an incompatible API or ABI, although features will generally not
65 comes in conflict with backwards compatibility, we will put security first,
87 ## Long-time support branches
90 compatibility (same definition as API except with re-linking instead of
91 re-compiling) and to avoid any increase in code size or RAM usage, or in the
98 For contributors, see the [Backwards Compatibility section of
99 CONTRIBUTING](CONTRIBUTING.md#backwards-compatibility).
105 - [master](https://github.com/Mbed-TLS/mbedtls/tree/master)
106 - [`development`](https://github.com/Mbed-TLS/mbedtls/)
107 - [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28)
109   <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.7>.