blob: d5144188ea229d65f53f45ca394da30852a0dd9e [file] [log] [blame] [view]
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +01001# Maintained branches
2
3At any point in time, we have a number of maintained branches consisting of:
4
Gilles Peskine991bbe72021-03-16 12:05:16 +01005- The [`master`](https://github.com/ARMmbed/mbedtls/tree/master) branch:
6 this always contains the latest release, including all publicly available
7 security fixes.
Gilles Peskinea23df132021-03-16 12:04:44 +01008- The [`development`](https://github.com/ARMmbed/mbedtls/tree/development) branch:
9 this is where new features land,
10 as well as bug fixes and security fixes.
11- One or more long-time support (LTS) branches:
12 these only get bug fixes and security fixes.
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010013
14We use [Semantic Versioning](https://semver.org/). In particular, we maintain
Gilles Peskine991bbe72021-03-16 12:05:16 +010015API compatibility in the `master` branch between major version changes. We
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010016also maintain ABI compatibility within LTS branches; see the next section for
17details.
18
19## Backwards Compatibility
20
Gilles Peskinea23df132021-03-16 12:04:44 +010021We maintain API compatibility in released versions of Mbed TLS. If you have
22code that's working and secure with Mbed TLS x.y.z and does not rely on
23undocumented features, then you should be able to re-compile it without
24modification with any later release x.y'.z' with the same major version
25number, and your code will still build, be secure, and work.
26
27There are rare exceptions: code that was relying on something that became
28insecure in the meantime (for example, crypto that was found to be weak) may
29need to be changed. In case security comes in conflict with backwards
30compatibility, we will put security first, but always attempt to provide a
31compatibility option.
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010032
33For the LTS branches, additionally we try very hard to also maintain ABI
34compatibility (same definition as API except with re-linking instead of
35re-compiling) and to avoid any increase in code size or RAM usage, or in the
36minimum version of tools needed to build the code. The only exception, as
37before, is in case those goals would conflict with fixing a security issue, we
38will put security first but provide a compatibility option. (So far we never
39had to break ABI compatibility in an LTS branch, but we occasionally had to
40increase code size for a security fix.)
41
Manuel Pégourié-Gonnard80c02af2021-02-25 12:34:58 +010042For contributors, see the [Backwards Compatibility section of
43CONTRIBUTING](CONTRIBUTING.md#cackwords-compatibility).
44
45## Current Branches
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010046
47The following branches are currently maintained:
48
Gilles Peskine991bbe72021-03-16 12:05:16 +010049- [master](https://github.com/ARMmbed/mbedtls/tree/master)
Gilles Peskinea23df132021-03-16 12:04:44 +010050- [`development`](https://github.com/ARMmbed/mbedtls/)
51- [`mbedtls-2.16`](https://github.com/ARMmbed/mbedtls/tree/mbedtls-2.16)
Manuel Pégourié-Gonnard80c02af2021-02-25 12:34:58 +010052 maintained until at least the end of 2021, see
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010053 <https://tls.mbed.org/tech-updates/blog/announcing-lts-branch-mbedtls-2.16>
Manuel Pégourié-Gonnarde6997392021-02-25 11:40:08 +010054
55Users are urged to always use the latest version of a maintained branch.