Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(20 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 10 March 2026 ==
== Yocto Project Status 21 July 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Current Dev Position: YP 6.1 M2<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<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 12th Mar. 7:30am 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 Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 21st July 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 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/>
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.0.16 has been released
*YP 6.0.2 has been released
*YP 5.3.2 is due to be released
*YP 5.0.19 is due to release
*YP 6.0 M2 is in QA
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*YP 4.0.34 is in QA.
*Some invasive LICENSE changes have merged into master:
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
**We now require the LICENSE field to match SPDX identifiers.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
**The build will issue warnings when this isn’t the case.
*We have issues which need further work that will block M3:  
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**x86 kvm seemingly broken with certain CPU features (#16074)
**CLOSED is no longer a valid value.  
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**‘WITH’ license exceptions are now supported
**Failure to generate regression reports in release builds
Big thanks for Joshua for getting us to the point where we can finally clean this up!
*We also have issues we need to resolve before M3:
*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
**Allowing non-destructive git fetcher updates for bitbake-setup.
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
**Splitting wic into an external tool.
*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.
**Kernel rust support.
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
**Switching to pkg-config.
*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.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**How to improve DEBUG_BUILD?
**several qemu ‘hang’ type issues on ARM
**DISTRO_FEATURES defaults improvements.
**sometimes yocto-check-layer is showing checksum mismatch issues
**SBOM/cve-check changes.
**siggen reset issues (“ResourceWarning: unclosed transport”)
**Reconcile poky and OE-Core defaults templates.
**groff build race issues
**Switch to internal VNC server in QEMU
**intermittent ptest failures in many recipes
**update to glibc 2.43 so we can release a new uninative
*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.
*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 44:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2866 (last week 2908) (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: 1081 (last week 1103)
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 144 (14%) [last week 145 (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 M2:
*YP 6.0 M3 Build Date 2026-03-23
**Build Date: w/c 2026-07-20
*YP 6.0 M3 Release Date 2026-04-08
**Release Date: w/c 2026-08-03
*YP 6.0 M4 Build Date 2026-04-13
*6.1 M3:
*YP 6.0 M4 Release Date 2026-05-04
**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 5.0.19 due to release
*YP 5.3.2  is released.
**Release Date w/c 2026-07-13
*YP 4.0.34 is in QA.
*YP 6.0.3
*YP 5.3.3 Build Date 2026-03-16
**Build Date w/c 2026-08-10
*YP 5.3.3 Release Date 2026-04-01
**Release Date w/c 2026-08-24
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.20
*YP 5.0.17 Release Date 2026-04-15
**Build Date w/c 2026-08-17
*YP 4.0.35 Build Date 2026-04-06
**Release Date w/c 2026-08-31
*YP 4.0.35 Release Date 2026-04-22
 
*YP 5.3.4 Build Date 2026-04-20  
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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 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"