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.
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.
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.)
As for why we don't support Dunfell, it was originally released in 2020. For
the purposes of our reference work, "old" software does not enable new product
development. If you want to use Dunfell, I'd recommend going with an OSV. They
have the ability to backport, deal with security response, etc.
--Mark
On 5/3/22 10:06 AM, [email protected] wrote:
Hi Mark,
My recommendation is to use everything from the same branch for your
projects.
So if you are doing a pure Yocto Project (not PetaLinux) workflow, use
Honister.
Great, just saw it was updated today, thanks for pushing that one.
Related question - why is Xilinx targeting Honister giving that it is EOL as of
this month? Why not target an LTS release such as Dunfell or Kirkstone?
Thanks,
Chris
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#4993):
https://lists.yoctoproject.org/g/meta-xilinx/message/4993
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]]
-=-=-=-=-=-=-=-=-=-=-=-
