Change Details

//This page is under construction and not ready for public review// **Overview** A very important criterion for evaluating and adopting a software platform is support. The Trusted Firmware-A community has been releasing code from the tip every six months. This model works very well for software innovation and supporting new hardware features. But for platforms in production, it leaves a hole in terms of maintenance, backward compatibility of important software fixes, and overall product lifecycle management. Several open source software projects (e.g. Ubuntu, Yocto, Linux Kernel) have faced this problem during their lifetime and have relied on a long term support policy to address this concern. Long-term support extends the period of software maintenance; it also alters the type and frequency of software updates (patches) to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not necessarily imply technical support. This document proposes a plan to rely on the path chosen by various open source software projects and define a long-term support policy. This proposal will not succeed without the support of the community and relies on contributions from Arm, its partners and platform owners. **Motivation** The following are some of the problems faced by a typical vendor when maintaining a software version downstream # The cost to maintain a software release and keep it updated with important software changes from upstream is too high # The cost to productize a newly released version is too high # Lack of pre-defined tests upstream means the code cannot be immediately deployed to the field # Some aspects like documentation, code analysis reports, long term tool availability are unclear The technical forum for TF-A on 10 Sep, 2020 was focused on this topic to gauge interest and support from the community. To move the discussion forward, this page intends to capture ideas from the community and eventually crystalize a plan that works for everyone. **Proposal** The following would be the expectations from a long-term support release branch. # 100% test coverage with a publicly available report for every changelist # Well defined policy to detect, report and deploy software fixes for mitigating security issues, stability concerns, erratas and bugs # Up-to-date API reference manual at any given changelist # Well documented performance numbers for important use cases # Usage of Long-term supported toolchains # Well defined policy for accepting new changes # Use of publicly available static analysis tools to improve code quality # Well defined release cadence and key quality indicators for each sub-release **References** - Tech forum discussion (https://www.trustedfirmware.org/meetings/tf-a-technical-forum/) on 10 Sep, 2020.

//This page is under construction and not ready for public review// **Overview** A very important criterion for evaluating and adopting a software platform is support. The Trusted Firmware-A community has been releasing code from the tip every six months. This model works very well for software innovation and implementing new hardware features. But for platforms in production, this policy does not scale in terms of maintenance, backward compatibility of important software fixes, and overall product lifecycle management. Several open source software projects (e.g. Ubuntu, Yocto, Linux Kernel) have faced this problem during their lifetime and have implemented a long term support release as a solution. Long-term support extends the period of software maintenance; it also alters the type and frequency of software updates (patches) to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not necessarily imply technical support. This document proposes a plan to leverage the path chosen by various open source software projects and define a long-term support release strategy. This proposal will not succeed without the support of the community and relies on contributions from Arm, its partners and platform owners. **Current problems** The following are some of the problems slowing down device upgrades. # The investment to maintain a software release and keep it updated with important software changes from upstream is too high # The cost to productize and deploy a newly released version is too high # Lack of pre-defined tests in the upstream codebase means that a new public release cannot be immediately deployed to the field # Some aspects like documentation, code analysis reports, test reports and long term availability of tools are not available The technical forum for TF-A on 10 Sep, 2020 was focused on this topic to gauge interest and support from the community. To move the discussion forward, this page intends to capture ideas from the community and eventually crystalize a plan that works for everyone. **Proposal** There is interest from the community to explore the possibility of a long-term release codebase to solve these problems. The following might be some of the expectations from a long-term support release branch. # 100% test coverage with a publicly available report for every changelist # Well defined policy to detect, report and deploy software fixes for mitigating security issues, stability concerns, erratas and bugs # Up-to-date API reference manual at any given changelist # Well documented performance numbers for important use cases # Usage of Long-term supported toolchains # Well defined policy for accepting new changes # Use of publicly available static analysis tools to improve code quality # Well defined release cadence and key quality indicators **Call to action** Reviewers are encouraged to add to the list of improvement areas and provide expectations from the long-term support release. This will help us define the problem before we start discussing the mechanics of the release. **References** - Tech forum discussion (https://www.trustedfirmware.org/meetings/tf-a-technical-forum/) on 10 Sep, 2020.

//This page is under construction and not ready for public review// **Overview** A very important criterion for evaluating and adopting a software platform is support. The Trusted Firmware-A community has been releasing code from the tip every six months. This model works very well for software innovation and supporimplementing new hardware features. But for platforms in production, it leaves a holethis policy does not scale in terms of maintenance, backward compatibility of important software fixes, and overall product lifecycle management. Several open source software projects (e.g. Ubuntu, Yocto, Linux Kernel) have faced this problem during their lifetime and have relied onimplemented a long term support policy to address this concernrelease as a solution. Long-term support extends the period of software maintenance; it also alters the type and frequency of software updates (patches) to reduce the risk, expense, and disruption of software deployment, while promoting the dependability of the software. It does not necessarily imply technical support. This document proposes a plan to rely onleverage the path chosen by various open source software projects and define a long-term support policyrelease strategy. This proposal will not succeed without the support of the community and relies on contributions from Arm, its partners and platform owners. **Motivation****Current problems** The following are some of the problems faced by a typical vendor when maintaining a software version downstreamslowing down device upgrades. # The costinvestment to maintain a software release and keep it updated with important software changes from upstream is too high # The cost to productize and deploy a newly released version is too high # Lack of pre-defined tests in the upstream codebase means the codeat a new public release cannot be immediately deployed to the field # Some aspects like documentation, code analysis reports, long term tooltest reports and long term availability of tools are unclearnot available The technical forum for TF-A on 10 Sep, 2020 was focused on this topic to gauge interest and support from the community. To move the discussion forward, this page intends to capture ideas from the community and eventually crystalize a plan that works for everyone. **Proposal** The following would bere is interest from the community to explore the possibility of a long-term release codebase to solve these problems. The following might be some of the expectations from a long-term support release branch. # 100% test coverage with a publicly available report for every changelist # Well defined policy to detect, report and deploy software fixes for mitigating security issues, stability concerns, erratas and bugs # Up-to-date API reference manual at any given changelist # Well documented performance numbers for important use cases # Usage of Long-term supported toolchains # Well defined policy for accepting new changes # Use of publicly available static analysis tools to improve code quality # Well defined release cadence and key quality indicators for each sub-release **Call to action** Reviewers are encouraged to add to the list of improvement areas and provide expectations from the long-term support release. This will help us define the problem before we start discussing the mechanics of the release. **References** - Tech forum discussion (https://www.trustedfirmware.org/meetings/tf-a-technical-forum/) on 10 Sep, 2020.