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| v2.4 | 2nd week of Nov '20 | 4th week of Oct '20 | 46+-----------------+---------------------------+------------------------------+ 47| v2.5 | 3rd week of May '21 | 5th week of Apr '21 | 48+-----------------+---------------------------+------------------------------+ 49| v2.6 | 4th week of Nov '21 | 2nd week of Nov '21 | 50+-----------------+---------------------------+------------------------------+ 51| v2.7 | 5th week of May '22 | 3rd week of May '22 | 52+-----------------+---------------------------+------------------------------+ 53| v2.8 | 5th week of Nov '22 | 3rd week of Nov '22 | 54+-----------------+---------------------------+------------------------------+ 55| v2.9 | 1st week of May '23 | 3rd week of Apr '23 | 56+-----------------+---------------------------+------------------------------+ 57 58Removal of Deprecated Interfaces 59-------------------------------- 60 61As mentioned in the :ref:`Platform Ports Policy`, this is a live document 62cataloging all the deprecated interfaces in TF-A project and the Release version 63after which it will be removed. 64 65+--------------------------------+-------------+---------+---------------------------------------------------------+ 66| Interface | Deprecation | Removed | Comments | 67| | Date | after | | 68| | | Release | | 69+================================+=============+=========+=========================================================+ 70| plat_convert_pk() function | Nov'22 | Next | Platform conversion to manage specific PK hash | 71| | | release | | 72| | | after | | 73| | | 2.8 | | 74+--------------------------------+-------------+---------+---------------------------------------------------------+ 75 76-------------- 77 78*Copyright (c) 2018-2022, Arm Limited and Contributors. All rights reserved.* 79