...
- Need to limit the number of hardware platforms that are supported for the LTS version only to the boards that are being put into production by members.
- Limit to Reference Hardware System Architecture compliant architectures?
- Instrument cluster reference hardware?
- Probably want to limit which components are maintained. For example bluez may not be included because it is a replaceable component that we think will be used by the device creators.
- AGL demo may not be maintained but we still need to build a binary that runs on the supported platforms so that we can test it.
- APIs will be stable over the lifetime of the LTS version.
- Need a strategy for how to accept patches into the LTS that may be different from the development model we use today.
- Gain agreement from commercial stakeholders, especially SOC vendors, that they will support the AGL LTS.
- For SOC vendors this will requirement an agreement to maintain their BSP, kernel version, and graphics stack for the life of the LTS.
- For OEM and Tier One members this will requirement an agreement that they will contribute fixes back to the AGL LTS effort.
General LTS in open source industry
- Not done by the project itself beyond two years typically. Usually is taken over by a commercial company
- Yocto provides no long-term support beyond 18 - 24 months. Usual expectation is that a commercial company can be contracted to maintain packages beyond that time-frame.
Next Steps
- Gather and consolidate requirements for review by the SAT and TSC by the June 6 SAT call. Team will consist of Walt, Panasonic, Denso, Toyota, VW, MB.