1Release Processes 2================= 3 4Project Release Cadence 5----------------------- 6 7The project currently aims to do a release once every 6 months which will be 8tagged on the master branch. There will be a code freeze (stop merging 9non-essential changes) up to 4 weeks prior to the target release date. The release 10candidates will start appearing after this and only bug fixes or updates 11required for the release will be merged. The maintainers are free to use their 12judgement on what changes are essential for the release. A release branch may be 13created after code freeze if there are significant changes that need merging onto 14the integration branch during the merge window. 15 16The release testing will be performed on release candidates and depending on 17issues found, additional release candidates may be created to fix the issues. 18 19:: 20 21 |<----------6 months---------->| 22 |<---4 weeks--->| |<---4 weeks--->| 23 +-----------------------------------------------------------> time 24 | | | | 25 code freeze ver w.x code freeze ver y.z 26 27 28Upcoming Releases 29~~~~~~~~~~~~~~~~~ 30 31These are the estimated dates for the upcoming release. These may change 32depending on project requirement and partner feedback. 33 34+-----------------+---------------------------+------------------------------+ 35| Release Version | Target Date | Expected Code Freeze | 36+=================+===========================+==============================+ 37| v2.0 | 1st week of Oct '18 | 1st week of Sep '18 | 38+-----------------+---------------------------+------------------------------+ 39| v2.1 | 5th week of Mar '19 | 1st week of Mar '19 | 40+-----------------+---------------------------+------------------------------+ 41| v2.2 | 4th week of Oct '19 | 1st week of Oct '19 | 42+-----------------+---------------------------+------------------------------+ 43| v2.3 | 4th week of Apr '20 | 1st week of Apr '20 | 44+-----------------+---------------------------+------------------------------+ 45 46Removal of Deprecated Interfaces 47-------------------------------- 48 49As mentioned in the :ref:`Platform Compatibility Policy`, this is a live 50document cataloging all the deprecated interfaces in TF-A project and the 51Release version after which it will be removed. 52 53+--------------------------------+-------------+---------+---------------------------------------------------------+ 54| Interface | Deprecation | Removed | Comments | 55| | Date | after | | 56| | | Release | | 57+================================+=============+=========+=========================================================+ 58| ``AARCH32``/``AARCH64`` macros | Oct '19 | v2.3 | Deprecated in favor of ``__aarch64__`` | 59+--------------------------------+-------------+---------+---------------------------------------------------------+ 60| ``__ASSEMBLY__`` macro | Oct '19 | v2.3 | Deprecated in favor of ``__ASSEMBLER__`` | 61+--------------------------------+-------------+---------+---------------------------------------------------------+ 62| Prototype SPCI-based SPM | Oct '19 | v2.2 | Based on outdated Alpha 1 spec. Will be replaced with | 63| (services/std_svc/spm) | | | alternative methods of secure partitioning support. | 64+--------------------------------+-------------+---------+---------------------------------------------------------+ 65 66-------------- 67 68*Copyright (c) 2018-2020, Arm Limited and Contributors. All rights reserved.* 69