...
- Code Maintained by AGL
- Source code and recipes will be maintained in such a way that builds are reproducible over the lifetime of the LTS version.
- Host system will be limited to the container that is shipped with the initial LTS version. AGL will ensure that the container is supported on the latest host system. (i.e. As Fedora or other distributions evolve the AGL container will still be able to be built)
- 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.
- Test image or images that allow AGL to be tested
- Once we have defined the APIs that are supported in the AGL LTS we can use the recipes to derive the upstream packages that need to be maintained and reproducible.
- APIs will be stable over the lifetime of the LTS version.
- APIs will be well specified and documented in a common format
- Security patches and bug-fixes will be backported from latest AGL version to LTS version.
- Source code and recipes will be maintained in such a way that builds are reproducible over the lifetime of the LTS version.
...
- 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.
- Notes from meeting in Berlin on 26 Sep
AI: identify base services (What is in core-image-minimal that is available in all profiles.)
* lifecycle
* apps vs platform (Which apps are maintained as part of the LTS)
*
* API definition & documentation & Schema
* AI: iot.bzh will follow-up on https://jira.automotivelinux.org/browse/SPEC-1903
* e.g. what about new things like: https://fuchsia.googlesource.com/docs/+/ea2fce2874556205204d3ef70c60e25074dc7ffd/development/languages/fidl/tutorial.md
* Follow-up on SAT
* API versions
* -> APPFW / Jose* 'core' LTS vs. IVI or Cluster LTS
* depends on changes required e.g. by IC