Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
 
Line 1: Line 1:
== Yocto Project Status 16 June 2026 ==
== Yocto Project Status 23 June 2026 ==
Current Dev Position: YP 6.1 M2<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>
Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 18th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 25th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 16th June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 23rd June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 18th June 10am GMT and Monday 22nd June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 25th June 10am GMT and Monday 29th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)


'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 6.0.1 is due for release
*YP 6.0.1 was released
*YP 6.1 M1 is in QA
*YP 6.1 M1 is in review
*AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
*CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
*Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
*Intermittent build failures continue to be problematic:
*AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.
**several qemu ‘hang’ type issues
*We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues - the qemu upgrade merged, at least some issues still occur
**sometimes yocto-check-layer is showing checksum mismatch issues
**sometimes yocto-check-layer is showing checksum mismatch issues
**siggen reset issues (“ResourceWarning: unclosed transport”)
**siggen reset issues (“ResourceWarning: unclosed transport”)
**groff build race issues
**groff build race issues
**intermittent ptest failures in many recipes (python3-click was tweaked)
**intermittent ptest failures in many recipes
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 37: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2590 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2620 (last week 2590) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1061 (last week 1056)
**Total patches found: 1054(last week 1061)
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**Patches in the Pending State: 145 (14%) [last week 146 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


Latest revision as of 14:50, 23 June 2026

Yocto Project Status 23 June 2026

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

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.0.1 was released
  • YP 6.1 M1 is in review
  • AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
  • CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
  • Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
  • We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
  • We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
  • Intermittent build failures continue to be problematic:
    • several qemu ‘hang’ type issues
    • 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
  • We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M1:
    • Build Date: w/c 2026-06-08
    • Release Date: w/c 2026-06-22
  • 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:

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=86842"