blob: 8b6d1965b1caaeb2cca2e8fc2e1e7cc1c2568d66 [file] [log] [blame]
Soby Mathew6325be52020-06-17 13:58:51 +01001Release Cadence and Process
2===========================
3
4Project Release Cadence
5-----------------------
6
7The project currently aims to do a release once every 4 months which will be
8tagged on the master branch. There will be a code freeze (stop merging
9non-essential changes) up to 3 weeks prior to the target release date. The
10release candidates will start appearing after this and only bug fixes or
11updates required for the release will be merged. The maintainers are free
12to use their judgement on what changes are essential for the release.
13
14The release testing will be performed on release candidates and depending on
15issues found, additional release candidates may be created to fix the issues.
16
17::
18
19 |<------------4 months----------->|
20 |<--upto 3 weeks-->| |<--upto 3 weeks-->|
21 +----------------------------------------------------- ----------> time
22 | | | |
23 code freeze ver w.x code freeze ver y.z
24
25Although this document specifies the release cadence, this does not preclude
26an adhoc release for specific project requirements.
27
Minos Galanakis3568bea2020-11-16 20:15:48 +000028Release Version Scheme
29----------------------
30
31Trusted Firmware-M uses a semantic versioning scheme. A version number is
32compiled as a dot separated set of numbers:
33
34**TF-Mv<MAJOR>.<MINOR>.<HOTFIX>**
35
36- <MAJOR>: Major release version for significant feature and API changes.
37- <MINOR>: Minor release version for incremental features and API changes.
38- <HOTFIX>: Used only for backporting **critical bug fix/security patches**.
39
Soby Mathew6325be52020-06-17 13:58:51 +010040--------------
41
42*Copyright (c) 2020, Arm Limited. All rights reserved.*