31 lines
1.3 KiB
ReStructuredText
31 lines
1.3 KiB
ReStructuredText
Release Cadence and Process
|
|
===========================
|
|
|
|
Project Release Cadence
|
|
-----------------------
|
|
|
|
The project currently aims to do a release once every 4 months which will be
|
|
tagged on the master branch. There will be a code freeze (stop merging
|
|
non-essential changes) up to 3 weeks prior to the target release date. The
|
|
release candidates will start appearing after this and only bug fixes or
|
|
updates required for the release will be merged. The maintainers are free
|
|
to use their judgement on what changes are essential for the release.
|
|
|
|
The release testing will be performed on release candidates and depending on
|
|
issues found, additional release candidates may be created to fix the issues.
|
|
|
|
::
|
|
|
|
|<------------4 months----------->|
|
|
|<--upto 3 weeks-->| |<--upto 3 weeks-->|
|
|
+----------------------------------------------------- ----------> time
|
|
| | | |
|
|
code freeze ver w.x code freeze ver y.z
|
|
|
|
Although this document specifies the release cadence, this does not preclude
|
|
an adhoc release for specific project requirements.
|
|
|
|
--------------
|
|
|
|
*Copyright (c) 2020, Arm Limited. All rights reserved.*
|