Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(124 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 16th, 2024 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday July 18th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 23rd July 7:30am 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)
*Weekly Project Engineering Sync - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.20 is in QA
*YP 6.0.2 has been released
*YP 5.1 M2 is due to be built now SPDX 3.0 has merged
*YP 5.0.19 is due to release
*SPDX 3.0 has merged, thanks Joshua, Marta and everyone else who has worked on this.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*We’ve chosen to make SPDX 3.0 the default since it is much more suited to what we do.
*Some invasive LICENSE changes have merged into master:
*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.
**We now require the LICENSE field to match SPDX identifiers.  
*If layers choose to change ERROR_QA, please do it on a per layer basis with an override, not globally,
**The build will issue warnings when this isn’t the case.
*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.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*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.
**CLOSED is no longer a valid value.  
*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.
**‘WITH’ license exceptions are now supported
*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/
Big thanks for Joshua for getting us to the point where we can finally clean this up!
*Some larger patches still need help with review these would be appreciated:
*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
**Improved CVE tooling from Marta
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
**kernel fitimage changes from Adrian
*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
**bitbake-setup and configuration fragments from Alexander
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*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’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
*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.
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**several qemu ‘hang’ type issues on ARM
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**intermittent ptest failures in many recipes
*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*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!
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*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
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2787 (last week 2822) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1075)
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 178 (16%) [last week 178 (17%)]
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 5.1 M2 Build date 2024-07-08
*6.1 M2:
*YP 5.1 M2 Release date 2024-07-19
**Build Date: w/c 2026-07-20
*YP 5.1 M3 Build date 2024-08-26
**Release Date: w/c 2026-08-03
*YP 5.1 M3 Release date 2024-09-06
*6.1 M3:
*YP 5.1 M4 Build date 2024-09-30
**Build Date: w/c 2026-08-31
*YP 5.1 M4 Release date 2024-10-25
**Release Date: w/c 2026-09-14
*6.1.0:
**Build Date (M4): w/c 2026-10-12
**Release Date: w/c 2026-11-02


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.20 is in QA
*YP 5.0.19 due to release
*YP 5.0.3 Build Date 2024-08-12
**Release Date w/c 2026-07-13
*YP 5.0.3 Release Date 2024-08-23
*YP 6.0.3
*YP 4.0.21 Build Date 2024-09-09
**Build Date w/c 2026-08-10
*YP 4.0.21 Release Date 2024-09-20
**Release Date w/c 2026-08-24
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.20
*YP 5.0.4 Release Date 2024-10-04
**Build Date w/c 2026-08-17
*YP 4.0.22 Build Date 2024-10-14
**Release Date w/c 2026-08-31
*YP 4.0.22 Release Date 2024-10-25
 
*YP 5.0.5 Build Date 2024-11-11
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 69: Line 77:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:50, 21 July 2026

Yocto Project Status 21 July 2026

Current Dev Position: YP 6.1 M2
Next Deadline: YP 6.1 M2: w/c 2026-07-20

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 6.0.2 has been released
  • YP 5.0.19 is due to release
  • YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
  • Some invasive LICENSE changes have merged into master:
    • We now require the LICENSE field to match SPDX identifiers.
    • The build will issue warnings when this isn’t the case.
    • Non SPDX licenses will need to be of the form LicenseRef-XXX
    • CLOSED is no longer a valid value.
    • ‘WITH’ license exceptions are now supported

Big thanks for Joshua for getting us to the point where we can finally clean this up!

  • We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
  • Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
  • A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
  • Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
    • We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
    • several qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • groff build race issues
    • intermittent ptest failures in many recipes
  • For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2:
    • Build Date: w/c 2026-07-20
    • Release Date: w/c 2026-08-03
  • 6.1 M3:
    • Build Date: w/c 2026-08-31
    • Release Date: w/c 2026-09-14
  • 6.1.0:
    • Build Date (M4): w/c 2026-10-12
    • Release Date: w/c 2026-11-02

Upcoming dot releases:

  • YP 5.0.19 due to release
    • Release Date w/c 2026-07-13
  • YP 6.0.3
    • Build Date w/c 2026-08-10
    • Release Date w/c 2026-08-24
  • YP 5.0.20
    • Build Date w/c 2026-08-17
    • Release Date w/c 2026-08-31

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

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86852"