Weekly Status

Yocto Project Weekly Status July 16th, 2024

Current Dev Position: YP 5.1 M2
Next Deadline: YP 5.1 M2 Build 8 July 2024

Next Team Meetings:

• Bug Triage meeting Thursday July 18th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
• Weekly Engineering Sync Tuesday July 16th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
• Twitch - See https://www.twitch.tv/theyoctojester

Key Status/Updates:

• YP 4.0.20 is in QA
• YP 5.1 M2 is due to be built now SPDX 3.0 has merged
• SPDX 3.0 has merged, thanks Joshua, Marta and everyone else who has worked on this.
• We’ve chosen to make SPDX 3.0 the default since it is much more suited to what we do.
• A number of QA checks were moved from WARN_QA to ERROR_QA. The intention is to allow recipes to be marked up with known issues rather than have builds with warnings people tend to ignore, or ideally have the issues fixed.
• If layers choose to change ERROR_QA, please do it on a per layer basis with an override, not globally,
• An upcoming version of Yocto Project Compatible will require some subset of the ERROR_QA checks to be tested and passed for the layer to be compatible.
• Debug optimization handling was changed, the DEBUG_FLAGS variable was dropped in favor of a new DEBUG_LEVELFLAG which allows distros to more easily change recipe debug levels, in particular to control size.
• The autobuilder has been running into space issues and we analyzed space usage in a build. Patches are proposed to drop the debug symbols for on target llvm to reduce space usage (along with teaks to qemu and openssl) as the output size is effectively unusable currently. Further work on minimizing disk usage would be very welcome and there is a direct relationship with build speed too.
• Autobuilder test result/output indexing has been moved to a specific autobuilder job so the work is more visible to all users (the ‘indexing’ builder). The script has been optimized and the output html cleaned up by Sovereign Tech *Fund sponsorship through their contractors: https://autobuilder.yocto.io/pub/non-release/
• Some larger patches still need help with review these would be appreciated:
  • Improved CVE tooling from Marta
  • kernel fitimage changes from Adrian
  • bitbake-setup and configuration fragments from Alexander
• There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
• We continue to have trouble tracking down the rust reproducibility problem in rustdoc. We tested rust 1.78 with master and there is a long list of reported issues on the mailing list unfortunately. Rust 1.77 has a much smaller list of problems at least in initial testing.

Ways to contribute:

• As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
• There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
• There are bugs that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
• We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
• Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
• Help us resolve CVE issues: CVE metrics
• We have a growing number of bugs in bugzilla, any help with them is appreciated.

Tracking Metrics:

• WDD 2787 (last week 2822) (https://wiki.yoctoproject.org/charts/combo.html)
• OE-Core/Poky Patch Metrics
  • Total patches found: 1082 (last week 1075)
  • Patches in the Pending State: 178 (16%) [last week 178 (17%)]
• https://autobuilder.yocto.io/pub/non-release/patchmetrics/

YP 5.1 Milestone Dates:

• YP 5.1 M2 Build date 2024-07-08
• YP 5.1 M2 Release date 2024-07-19
• YP 5.1 M3 Build date 2024-08-26
• YP 5.1 M3 Release date 2024-09-06
• YP 5.1 M4 Build date 2024-09-30
• YP 5.1 M4 Release date 2024-10-25

Upcoming dot releases:

• YP 4.0.20 is in QA
• YP 5.0.3 Build Date 2024-08-12
• YP 5.0.3 Release Date 2024-08-23
• YP 4.0.21 Build Date 2024-09-09
• YP 4.0.21 Release Date 2024-09-20
• YP 5.0.4 Build Date 2024-09-23
• YP 5.0.4 Release Date 2024-10-04
• YP 4.0.22 Build Date 2024-10-14
• YP 4.0.22 Release Date 2024-10-25
• YP 5.0.5 Build Date 2024-11-11
• YP 5.0.5 Release Date 2024-11-22
• YP 4.0.23 Build Date 2024-11-18
• YP 4.0.23 Release Date 2024-11-29

The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:
https://wiki.yoctoproject.org/wiki/TSC

Archives

• 2024 Yocto Project Weekly Status Archive
• 2023 Yocto Project Weekly Status Archive
• 2022 Yocto Project Weekly Status Archive
• 2021 Yocto Project Weekly Status Archive
• 2020 Yocto Project Weekly Status Archive
• 2019 Yocto Project Weekly Status Archive
• 2018 Yocto Project Weekly Status Archive