Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(11 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 31 March 2026 ==
== Yocto Project Status 9 June 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Current Dev Position: YP 6.1 M1<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>
Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th 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 4.0.34 was released.
*YP 5.0.18 has been released
*YP 5.3.3 is approved for release.
*YP 6.0.1 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.1 M1 is due to build this week
*YP 6.0 M3 is now due to build however there are still key changes missing.
*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
*Issues still pending:
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
**Splitting wic into an external tool.
*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
**Converting scripts/run-cvecheck to sbom-cve-check
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
**DISTRO_FEATURES defaults improvements.
*Intermittent build failures continue to be problematic and unchanged from last week:
**RHEL 9 xattrs/selinux/tar issue
**several qemu ‘hang’ type issues
**How to improve DEBUG_BUILD?
**sometimes yocto-check-layer is showing checksum mismatch issues
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
**siggen reset issues (“ResourceWarning: unclosed transport”)
*Issues that are mostly known quantities still needing work:
**groff build race issues
**x86 kvm seemingly broken with certain CPU features (#16074)
**intermittent ptest failures in many recipes
**Failure to generate regression reports in release builds
*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
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp


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


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


'''YP 6.0 Milestone Dates:'''<br/>
'''Upcoming development releases:'''<br/>
*YP 6.0 M3 Build Date 2026-03-23
*6.1 M1:
*YP 6.0 M3 Release Date 2026-04-08
**Build Date: w/c 2026-06-08
*YP 6.0 M4 Build Date 2026-04-13
**Release Date: w/c 2026-06-22
*YP 6.0 M4 Release Date 2026-05-04
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.34 was released.
*YP 6.0.1 is in QA.
*YP 5.3.3 ready for release.
*YP 6.0.2
*YP 5.0.17 Build Date 2026-03-30
**Build Date w/c 2026-06-23
*YP 5.0.17 Release Date 2026-04-15
**Release Date w/c 2026-07-06
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.19
*YP 4.0.35 Release Date 2026-04-22
**Build Date w/c 2026-06-30
*YP 5.3.4 Build Date 2026-04-20
**Release Date w/c 2026-07-13
*YP 5.3.4 Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05


'''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/>

Latest revision as of 08:13, 9 June 2026

Yocto Project Status 9 June 2026

Current Dev Position: YP 6.1 M1
Next Deadline: YP 6.1 M1: w/c 2026-06-08

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.18 has been released
  • YP 6.0.1 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.
  • Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
  • 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:
    • 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=86838"