Skip to contentSkip to conversation

Yocto Project LTS Proposal/Discussion

Openembedded-architecture Nicholas Krause 1 participant 1 message Oct 25, 2019 2 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

#2 lore raw
Quoted 3 lines · Rich Persaud

This came directly to me -- did you mean to copy the list?

Rich

Sorry misclick on my end Rich.

Nick

Quoted 68 lines
Quoted 68 lines · Nicholas Krause



Quoted 36 lines · Rich Persaud

/(adding the automated-testing list)/

Quoted 4 lines · Richard Purdie

I'm posting this to openembedded-architecture since it probably is the best place for discussions about OE/Yocto planning.

Quoted 8 lines

The Yocto Project TSC believes one of the things needed for YP and for OE is more information being pulled together about how an LTS release could work. The document linked to below is the information it was able to collate together on the subject. Its the result of some long discussions by the TSC.
...
The key thing needed to make this happen is a resource commitment to it. Without such a commitment it is simply not feasible.

Vendors who provide commercial support for OE/Yocto-based products may already be investing downstream resources for equivalent "LTS" support.  May be useful for the document to show the financial benefits of shifting a percentage of downstream LTS validation resources to upstream Yocto LTS.

Quoted 9 lines

There may be
new companies willing to join the project in order to make it happen, if so we should talk further.

The document:

https://docs.google.com/document/d/1AwAFDf52f_FoXksbHEVUMlu4hpcI0JMGVG-Kj_sUkyc/

The project components to be covered would need to match those

included in our standard release process and should be clearly defined. Those components would be:

Quoted 4 lines

Bitbake
OE-Core
Meta-yocto
yocto-docs

...

Quoted 1 line

For simplicity, it is also proposed that only automated testing be

used for testing the LTS and that any current manual QA is not performed.
...

Quoted 8 lines
Quoted 2 lines

Only run virtualized tests
Only support one host distro, an Ubuntu LTS as it has right lifespan

When the first Yocto LTS release is available, could that become the host distro for automated testing?  That would provide Yocto automated testing with supply chain integrity benefits from Yocto.  If we take that path, with automated testing based on virtualization, could we add meta-virtualization to the list of Yocto LTS release components?

Yocto-on-Yocto automated testing could reduce risks [1] that impact software supply chains. A potential topic for the ATS event [2] next week.

Rich

One concern on the toolchain or lanuage side  is what happens if something like a new C++ release happens or similar. Do you plan on allowing toolchain migration to using the newer version of a given lanuage.

May be worth considering,

Nick

Quoted 10 lines

[1] https://www.platformsecuritysummit.com/2019/speaker/sherman/

[2] https://elinux.org/Automated_Testing_Summit_2019

_______________________________________________
Openembedded-architecture mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-architecture