| Soby Mathew | 6325be5 | 2020-06-17 13:58:51 +0100 | [diff] [blame^] | 1 | Release Cadence and Process |
| 2 | =========================== |
| 3 | |
| 4 | Project Release Cadence |
| 5 | ----------------------- |
| 6 | |
| 7 | The project currently aims to do a release once every 4 months which will be |
| 8 | tagged on the master branch. There will be a code freeze (stop merging |
| 9 | non-essential changes) up to 3 weeks prior to the target release date. The |
| 10 | release candidates will start appearing after this and only bug fixes or |
| 11 | updates required for the release will be merged. The maintainers are free |
| 12 | to use their judgement on what changes are essential for the release. |
| 13 | |
| 14 | The release testing will be performed on release candidates and depending on |
| 15 | issues 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 | |
| 25 | Although this document specifies the release cadence, this does not preclude |
| 26 | an adhoc release for specific project requirements. |
| 27 | |
| 28 | -------------- |
| 29 | |
| 30 | *Copyright (c) 2020, Arm Limited. All rights reserved.* |