xref: /aosp_15_r20/external/arm-trusted-firmware/docs/about/release-information.rst (revision 54fd6939e177f8ff529b10183254802c76df6d08)
1*54fd6939SJiyong ParkRelease Processes
2*54fd6939SJiyong Park=================
3*54fd6939SJiyong Park
4*54fd6939SJiyong ParkProject Release Cadence
5*54fd6939SJiyong Park-----------------------
6*54fd6939SJiyong Park
7*54fd6939SJiyong ParkThe project currently aims to do a release once every 6 months which will be
8*54fd6939SJiyong Parktagged on the master branch. There will be a code freeze (stop merging
9*54fd6939SJiyong Parknon-essential changes) up to 4 weeks prior to the target release date. The release
10*54fd6939SJiyong Parkcandidates will start appearing after this and only bug fixes or updates
11*54fd6939SJiyong Parkrequired for the release will be merged. The maintainers are free to use their
12*54fd6939SJiyong Parkjudgement on what changes are essential for the release. A release branch may be
13*54fd6939SJiyong Parkcreated after code freeze if there are significant changes that need merging onto
14*54fd6939SJiyong Parkthe integration branch during the merge window.
15*54fd6939SJiyong Park
16*54fd6939SJiyong ParkThe release testing will be performed on release candidates and depending on
17*54fd6939SJiyong Parkissues found, additional release candidates may be created to fix the issues.
18*54fd6939SJiyong Park
19*54fd6939SJiyong Park::
20*54fd6939SJiyong Park
21*54fd6939SJiyong Park                            |<----------6 months---------->|
22*54fd6939SJiyong Park            |<---4 weeks--->|              |<---4 weeks--->|
23*54fd6939SJiyong Park       +-----------------------------------------------------------> time
24*54fd6939SJiyong Park            |               |              |               |
25*54fd6939SJiyong Park         code freeze       ver w.x       code freeze     ver y.z
26*54fd6939SJiyong Park
27*54fd6939SJiyong Park
28*54fd6939SJiyong ParkUpcoming Releases
29*54fd6939SJiyong Park~~~~~~~~~~~~~~~~~
30*54fd6939SJiyong Park
31*54fd6939SJiyong ParkThese are the estimated dates for the upcoming release. These may change
32*54fd6939SJiyong Parkdepending on project requirement and partner feedback.
33*54fd6939SJiyong Park
34*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
35*54fd6939SJiyong Park| Release Version |  Target Date              | Expected Code Freeze         |
36*54fd6939SJiyong Park+=================+===========================+==============================+
37*54fd6939SJiyong Park| v2.0            | 1st week of Oct '18       | 1st week of Sep '18          |
38*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
39*54fd6939SJiyong Park| v2.1            | 5th week of Mar '19       | 1st week of Mar '19          |
40*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
41*54fd6939SJiyong Park| v2.2            | 4th week of Oct '19       | 1st week of Oct '19          |
42*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
43*54fd6939SJiyong Park| v2.3            | 4th week of Apr '20       | 1st week of Apr '20          |
44*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
45*54fd6939SJiyong Park| v2.4            | 2nd week of Nov '20       | 4th week of Oct '20          |
46*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
47*54fd6939SJiyong Park| v2.5            | 3rd week of May '21       | 5th week of Apr '21          |
48*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
49*54fd6939SJiyong Park| v2.6            | 4th week of Nov '21       | 2nd week of Nov '21          |
50*54fd6939SJiyong Park+-----------------+---------------------------+------------------------------+
51*54fd6939SJiyong Park
52*54fd6939SJiyong ParkRemoval of Deprecated Interfaces
53*54fd6939SJiyong Park--------------------------------
54*54fd6939SJiyong Park
55*54fd6939SJiyong ParkAs mentioned in the :ref:`Platform Compatibility Policy`, this is a live
56*54fd6939SJiyong Parkdocument cataloging all the deprecated interfaces in TF-A project and the
57*54fd6939SJiyong ParkRelease version after which it will be removed.
58*54fd6939SJiyong Park
59*54fd6939SJiyong Park+--------------------------------+-------------+---------+---------------------------------------------------------+
60*54fd6939SJiyong Park| Interface                      | Deprecation | Removed | Comments                                                |
61*54fd6939SJiyong Park|                                | Date        | after   |                                                         |
62*54fd6939SJiyong Park|                                |             | Release |                                                         |
63*54fd6939SJiyong Park+================================+=============+=========+=========================================================+
64*54fd6939SJiyong Park|                                |             |         |                                                         |
65*54fd6939SJiyong Park+--------------------------------+-------------+---------+---------------------------------------------------------+
66*54fd6939SJiyong Park
67*54fd6939SJiyong Park--------------
68*54fd6939SJiyong Park
69*54fd6939SJiyong Park*Copyright (c) 2018-2021, Arm Limited and Contributors. All rights reserved.*
70