Hi all, I've re-read the policy on LTS backports / mixin repositories (https://wiki.yoctoproject.org/wiki/LTS#LTS_.E2.80.9CMixin.E2.80.9D_repositories) and have a few thoughts.
I don't think `oecore-backport-mixin` is a good name for two reasons. One is that we're introducing the new concept of "mixins" when these really would just be normal layers and I think new terminology would be potentially confusing. The second is that we may also want backports for things which exist in the meta-openembedded repository (let's say a new Postgresql version as an example). I propose we instead just call this `openembedded-backports`. I don't think the branching policy is ideal either. I'm not a fan of having unrelated code on different branches within the same repository. I think the backports repository should follow a similar layout to meta-openembedded where each small backport layer is a top-level directory within this repository and we'd just have a single `dunfell` branch in git for now. I think for various reasons I'll want to use u-boot 2020.07 on dunfell when it's released so I'd be happy to make that our first guinea pig backport if we can get the relevant pieces in place over the next couple of weeks. Thanks, -- Paul Barker Konsulko Group
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#1082): https://lists.openembedded.org/g/openembedded-architecture/message/1082 Mute This Topic: https://lists.openembedded.org/mt/74481727/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-architecture/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
