Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(19 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 17 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 19th 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 17th 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 19th Mar. 10am GMT and Monday 23rd 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.3.2 has been released
*YP 6.0.2 has been released
*YP 6.0 M2 is due to be released
*YP 5.0.19 is due to release
*YP 4.0.34 is in QA.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*Some invasive LICENSE changes have merged into master:
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
**We now require the LICENSE field to match SPDX identifiers.
*We have issues we need to resolve before M3:
**The build will issue warnings when this isn’t the case.
**x86 kvm seemingly broken with certain CPU features (#16074)
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**CLOSED is no longer a valid value.  
**Failure to generate regression reports in release builds
**‘WITH’ license exceptions are now supported
**Allowing non-destructive git fetcher updates for bitbake-setup.
Big thanks for Joshua for getting us to the point where we can finally clean this up!
**Splitting wic into an external tool.
*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
**Switching to pkg-config.
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
*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.
**How to improve DEBUG_BUILD?
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
**DISTRO_FEATURES defaults improvements.
*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.
**SBOM/cve-check changes.
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**Reconcile poky and OE-Core defaults templates.
**several qemu ‘hang’ type issues on ARM
**Resolve Fedora 43 selftest failures
**sometimes yocto-check-layer is showing checksum mismatch issues
*glibc was upgraded 2.43 and we released a new uninative to match
**siggen reset issues (“ResourceWarning: unclosed transport”)
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
**groff build race issues
*We are adding testing of ptests on musl to our test matrix
**intermittent ptest failures in many recipes
*Kernel rust support has merged
*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’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
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
Line 47: Line 44:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2841 (last week 2866) (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: 1069 (last week 1081)
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 152 (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 ready for release.
*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.3.2 is released.
*YP 5.0.19 due to release
*YP 4.0.34 is in QA.
**Release Date w/c 2026-07-13
*YP 5.3.3 is in QA.
*YP 6.0.3
*YP 5.0.17 Build Date 2026-03-30
**Build Date w/c 2026-08-10
*YP 5.0.17 Release Date 2026-04-15
**Release Date w/c 2026-08-24
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.20
*YP 4.0.35 Release Date 2026-04-22
**Build Date w/c 2026-08-17
*YP 5.3.4 Build Date 2026-04-20  
**Release Date w/c 2026-08-31
*YP 5.3.4 Release Date 2026-05-06
 
*YP 5.0.18 Build Date 2026-04-27
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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