docs/about/lts.rst

40 the risk of regression. At the same time the companies don't want to exclude
88 supported, how frequently should LTS releases be made and at which time(s) of
105 3. Which time(s) of the year should the releases be made?
111 releases are timed with Android release, this gives enough time to harden
114 the basis for LTS then developers will have little time -- about a month,
163 Though we are unlikely to update CI scripts, but time to time migrating a newer
174 Updates to the version of MbedTLS used with LTS will happen time to time based on
190 the LTS branch will be created at the same time as the TF-A November release,
203   diagram, at the same time LTS release candidate branch is made which is based
214   time that we had between Nov 2022 and early Feb 2023. This is because there
217 - Nov 2023: TF-A 2.10 is released. Not shown in the diagram, at the same time
234    at random points in time when there is a "candidate" patch
236    with a detailed description of the maximum time spent in each step
338 Above will buy us time to then work on the rest of the execution plan which
360    branches at any given point in time
381      time while the patch fix is time-critical and, hence slowing other