Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
 
Line 1: Line 1:
== Yocto Project Status 9 June 2026 ==
== Yocto Project Status 16 June 2026 ==
Current Dev Position: YP 6.1 M1<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<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 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 18th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 16th June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 18th June 10am GMT and Monday 22nd 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 5.0.18 has been released
*YP 6.0.1 is due for release
*YP 6.0.1 is in QA.
*YP 6.1 M1 is in QA
*YP 6.1 M1 is due to build this week
*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.
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
*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.
*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
*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
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
*Intermittent build failures continue to be problematic and unchanged from last week:
*Intermittent build failures continue to be problematic and unchanged from last week:
**several qemu ‘hang’ type issues
**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
**intermittent ptest failures in many recipes (python3-click was tweaked)
*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 36: Line 37:


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


Line 57: Line 58:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 6.0.1 is in QA.
*YP 6.0.1 is due to release
*YP 6.0.2
*YP 6.0.2
**Build Date w/c 2026-06-23
**Build Date w/c 2026-06-23

Latest revision as of 14:47, 16 June 2026

Yocto Project Status 16 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 is due for release
  • YP 6.1 M1 is in QA
  • 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
  • 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.
  • 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
    • siggen reset issues (“ResourceWarning: unclosed transport”)
    • groff build race issues
    • intermittent ptest failures in many recipes (python3-click was tweaked)
  • 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=86839"