Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(14 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 10 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 12th Mar. 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 10th 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 12th Mar. 10am GMT and Monday 16th Mar. 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 5.0.16 has been released
*YP 5.0.18 has been released
*YP 5.3.2 is due to be released
*YP 6.0.1 is in QA.
*YP 6.0 M2 is in QA
*YP 6.1 M1 is due to build this week
*YP 4.0.34 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.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.  
*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 issues which need further work that will block M3:
*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
**x86 kvm seemingly broken with certain CPU features (#16074)
*Intermittent build failures continue to be problematic and unchanged from last week:
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**several qemu ‘hang’ type issues
**Failure to generate regression reports in release builds
**sometimes yocto-check-layer is showing checksum mismatch issues
*We also have issues we need to resolve before M3:
**siggen reset issues (“ResourceWarning: unclosed transport”)
**Allowing non-destructive git fetcher updates for bitbake-setup.
**groff build race issues
**Splitting wic into an external tool.
**intermittent ptest failures in many recipes
**Kernel rust support.
*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
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!


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


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2866 (last week 2908) (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: 1081 (last week 1103)
**Total patches found: 1056 (last week 1087)
**Patches in the Pending State: 151 (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 M2 is in QA.
*6.1 M1:
*YP 6.0 M3 Build Date 2026-03-23
**Build Date: w/c 2026-06-08
*YP 6.0 M3 Release Date 2026-04-08
**Release Date: w/c 2026-06-22
*YP 6.0 M4 Build Date 2026-04-13
*6.1 M2:
*YP 6.0 M4 Release Date 2026-05-04
**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 5.0.16  is released.
*YP 6.0.1 is in QA.
*YP 5.3.2 is released.
*YP 6.0.2
*YP 4.0.34 is in QA.
**Build Date w/c 2026-06-23
*YP 5.3.3 Build Date 2026-03-16
**Release Date w/c 2026-07-06
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.19
*YP 5.0.17 Build Date 2026-03-30
**Build Date w/c 2026-06-30
*YP 5.0.17 Release Date 2026-04-15
**Release Date w/c 2026-07-13
*YP 4.0.35 Build Date 2026-04-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*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"