Lines Matching +full:- +full:y

5 - The [`main`](https://github.com/Mbed-TLS/mbedtls/tree/main) branch:
8 - The [`development`](https://github.com/Mbed-TLS/mbedtls/tree/development) branch:
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).
15 - [`mbedtls-3.6`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-3.6).
18 such as [`archive/mbedtls-2.7`](https://github.com/Mbed-TLS/mbedtls/tree/archive/mbedtls-2.7).
27 We will make regular LTS releases on an 18-month cycle, each of which will have
35 code that's working and secure with Mbed TLS x.y.z and does not rely on
36 undocumented features, then you should be able to re-compile it without
37 modification with any later release x.y'.z' with the same major version
41 compile-time configuration (`mbedtls/mbedtls_config.h`) or the same modified
42 compile-time configuration. Changing compile-time configuration options can
75 of Mbed TLS (for example, all Mbed TLS 3.y versions will be able to read
76 keys written under any Mbed TLS 3.x with x <= y).
79 LTS, but future major version upgrades (for example from 2.28.x/3.x to 4.y)
88 ## Long-time support branches
91 compatibility (same definition as API except with re-linking instead of
92 re-compiling) and to avoid any increase in code size or RAM usage, or in the
100 CONTRIBUTING](CONTRIBUTING.md#backwards-compatibility).
106 - [main](https://github.com/Mbed-TLS/mbedtls/tree/main)
107 - [`development`](https://github.com/Mbed-TLS/mbedtls/)
108 - [`mbedtls-3.6`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-3.6)
110   <https://github.com/Mbed-TLS/mbedtls/releases/tag/v3.6.0>.
111 - [`mbedtls-2.28`](https://github.com/Mbed-TLS/mbedtls/tree/mbedtls-2.28)
113   <https://github.com/Mbed-TLS/mbedtls/releases/tag/v2.28.8>.