Yocto: Difference between revisions
Appearance
Line 15: | Line 15: | ||
=== CI Approach [DRAFT] === | === CI Approach [DRAFT] === | ||
'''Scope:''' | |||
* The goal of the CI tooling is to automatically check the compatibility of the layers with regard to a certain release of the Yocto project in combination with a certain release in relation to a certain release of meta-qt{5|6} | |||
* The CI shall ensure that there is a documented compatible combination of Yocto meta-layers | |||
* The CI shall ensure that backports to older Yocto layers are compatible with older Bitbake versions and recipes | |||
=== Branch / Merge Strategy [DRAFT] === | === Branch / Merge Strategy [DRAFT] === |
Revision as of 12:56, 2 October 2022
Yocto [DRAFT]
KDE currently ships two Yocto meta layers that are supposed to ease the use of KDE Frameworks, Plasma and Applications for device creators.
- meta-kf5
- meta-kde
Usage
Layer Development
CI Approach [DRAFT]
Scope:
- The goal of the CI tooling is to automatically check the compatibility of the layers with regard to a certain release of the Yocto project in combination with a certain release in relation to a certain release of meta-qt{5|6}
- The CI shall ensure that there is a documented compatible combination of Yocto meta-layers
- The CI shall ensure that backports to older Yocto layers are compatible with older Bitbake versions and recipes
Branch / Merge Strategy [DRAFT]
- application releases are updated in the master branch
- exception is if the tracking branch for an old Yocto LTS release shall be updated to version older than in the master branch
- change from the master branch that shall be used for older Yocto releases shall be cherry-picked