On 5/6/22 12:23 PM, [email protected] wrote:
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?)

The software release includes Vivado, Vitis, all of the firmware components, openamp, FreeRTOS and other components. All of these items are aligned and release together, and unfortunately all of their schedules and the YP LTS do not align.

I recommend people talk to OSVs for long term support needs, including alignment with YP LTS, as that is not something that we are doing.

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.

Wouldn't matter if we'd chosen the LTS or Honister or another release. We do not patch the system once we doing our (roughly) 6 month releases. This is why I recommend working with an OSV and/or ISV. (Your company having an internal group acting as an OSV is equivalent.)

The key is that we're not an Operating System vendor, we're a silicon vendor who needs to enable operating systems. This could change in the future, but it's how we're currently aligned.

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.

My thinking right now, Langdale (current YP master) will be enabled with the current 2022.1 code, and I hope 2022.2 when it is released later this year.

Our alignment (product wise) with Langdale will probably be 2023.1 release. But this is simply a guess based on history and could change.

--Mark

Thanks,
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5021): 
https://lists.yoctoproject.org/g/meta-xilinx/message/5021
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]]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to