Sorry to retread old discussions. > As said before. We have historically done a spring and fall release, spring > needs to be based on the prior Yocto Project release in order for us to have > the necessary combination of stability, functionality and relevance. Thus the > prior fall release is used.
Sure, understood. > Kirkstone isn't out and stable prior to our spring release. YP support is a > tiny tiny part of the overall yearly release. So the timelines don't line up. Maybe for Xilinx, but YP is a pretty big part of using an SoC in an actual product though... (unless you have a pure FPGA design, in which case why use an SoC at all?) > My past experiences show that it takes a large software team from a few > weeks to months to adapt to a release (depending on how capable the > organization is to tracking master development.) Yes, we've done the upgrade several times and I'd say your timescale matches our experience as well. It's just unfortunate that when we upgrade to 2022.1 we will immediately need to pay the weeks/months unless we want a system with unpatched CVEs / BitBake bugs. I see in a recent email you say that Xilinx is targeting Langdale next. It looks like the timescales line up a little better there - the Yocto release schedule says it will be supported until May 2023, so that's pretty good. Thanks, Chris
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#5019): https://lists.yoctoproject.org/g/meta-xilinx/message/5019 Mute This Topic: https://lists.yoctoproject.org/mt/90852291/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
