You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My propsal is to intruduce yocto release branches (e.g. krikstone, mickledore) for backwards compatibility. When someone is using kirkstone, there are no surprises when meta-slint upgrades to a new yocto version.
The text was updated successfully, but these errors were encountered:
kkettinger
changed the title
Proposal: Introduce yocto release branches for backward compatibility
Proposal: Introduce yocto release branches for backwards compatibility
Jun 18, 2023
I think that makes sense to introduce when a divergence happens. Ideally master is usable with multiple yocto versions. But I guess that won't work for very long.
Too bad GitHub Actions are not suitable for CI - I'm concerned that multiple branches increase the amount of effort to maintain.
You are right, as long as there is no deviation between the versions, extra branches just increase the amount of work to do. I was just feeling uneasy including master as branch into my manifest file 😄
My propsal is to intruduce yocto release branches (e.g. krikstone, mickledore) for backwards compatibility. When someone is using kirkstone, there are no surprises when meta-slint upgrades to a new yocto version.
Yocto release names can be found here: https://wiki.yoctoproject.org/wiki/Releases
The text was updated successfully, but these errors were encountered: