docs/about/lts.rst

38 when a product is released, the companies have to support that in-market product
52 This means that companies have to maintain and backport critical updates to
66 We must have an objective criterion for selecting patches to be backported to
94 tends to have less churn and longer lifetime than a HLOS, TF-A is trying to
102 Given that many products that have a release cycle, have a yearly release
103 cycle, it would make sense to have yearly TF-A releases.
114 the basis for LTS then developers will have little time -- about a month,
257 down steps and does not have to make policy level decisions for merge, testing,
289 #. Some dependency patches, not listed in the CSV file, may have to be taken, to ease the
311    dedicated scripts for each LTS version which have to be updated manually. This is the case
314    There is no automation for those repositories. So the patches will have to be merged manually,
315    and for tf-a-ci-scripts and tf-a-tests, tags will also have to be set manually.
373 questions. They have been discussed on the mailing list too.
390      that will help accurately track what changes have been deployed in-field.
396 become real problems, then we will have concrete data and be better able to