docs/about/lts.rst

54 using TF-A, it makes sense to factor out this effort into a community-wide LTS.
75 #. Security advisories: Any patch that makes it into :ref:`Security Advisories`
95 support at-least 7 years for its LTS. Initially it was intended to support
103 cycle, it would make sense to have yearly TF-A releases.
108 on the November TF-A release has a few benefits. First, it aligns with Linux
109 LTS releases which happen towards the end of each year. Second, it aligns
112 the TF-A LTS release during development so that it's ready for launch in
119 5 years and we can discuss extending it to 7 years later on. The LTS release
184 Since the LTS branch will be used in product releases, it is expected that more
186 it would make sense to leave at least a month after the November release and
191 but it will be officially released at the end of January or early February.
193 ideally it coincides with TF-A November release which means that our test
205   We can call it `LTS 2.8-rc`.
208 - May 2023: TF-A 2.9 is released but since this is not an LTS branch it doesn’t
282    the v2.x.y release, and that it has the origin/lts-v2.x tag.
302    this CI run passes, it automatically applies the Verified+1 (V+1) label to
313    will be cherry-picked from master branch to the LTS branch the same way it is done for TF-A.
365    c. get it through the CI/CD testing flow
398 is not the final one. We will constantly be discussing it and deciding how to
399 adapt it as we see practical problems.