Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(17 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 31 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 Apr. 2nd 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 31st 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 Apr. 2nd 10am GMT and Monday Apr. 6th 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 4.0.34 was released.
*YP 6.0.2 has been released
*YP 5.3.3 is approved for release.
*YP 5.0.19 is due to release
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Some invasive LICENSE changes have merged into master:
*Issues still pending:
**We now require the LICENSE field to match SPDX identifiers.  
**Splitting wic into an external tool.
**The build will issue warnings when this isn’t the case.
**Converting scripts/run-cvecheck to sbom-cve-check
**Non SPDX licenses will need to be of the form LicenseRef-XXX
**DISTRO_FEATURES defaults improvements.
**CLOSED is no longer a valid value.  
**RHEL 9 xattrs/selinux/tar issue
**‘WITH’ license exceptions are now supported
**How to improve DEBUG_BUILD?
Big thanks for Joshua for getting us to the point where we can finally clean this up!
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*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
*Issues that are mostly known quantities still needing work:
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
**x86 kvm seemingly broken with certain CPU features (#16074)
*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.
**Failure to generate regression reports in release builds
*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*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.
*Issues that were resolved this week:
**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
**Sbom-cve-check added
**several qemu ‘hang’ type issues on ARM
**Replacement of runtlp with kirk (Thanks Daniel!)
**sometimes yocto-check-layer is showing checksum mismatch issues
**bitbake-setup vscode integration
**siggen reset issues (“ResourceWarning: unclosed transport”)
**Fedora 43 selftest failures
**groff build race issues
**Reconciling poky and OE-Core defaults templates.
**intermittent ptest failures in many recipes
*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.
*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, 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 44:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2814 (last week 2819) (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: 1062 (last week 1072)
**Total patches found: 1019 (last week 1019+)
**Patches in the Pending State: 148 (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 M3 Build Date 2026-03-23
*6.1 M2:
*YP 6.0 M3 Release Date 2026-04-08
**Build Date: w/c 2026-07-20
*YP 6.0 M4 Build Date 2026-04-13
**Release Date: w/c 2026-08-03
*YP 6.0 M4 Release Date 2026-05-04
*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 5.0.19 due to release
*YP 5.3.3 ready for release.
**Release Date w/c 2026-07-13
*YP 5.0.17 Build Date 2026-03-30
*YP 6.0.3
*YP 5.0.17 Release Date 2026-04-15
**Build Date w/c 2026-08-10
*YP 4.0.35 Build Date 2026-04-06
**Release Date w/c 2026-08-24
*YP 4.0.35 Release Date 2026-04-22
*YP 5.0.20
*YP 5.3.4 Build Date 2026-04-20  
**Build Date w/c 2026-08-17
*YP 5.3.4 Release Date 2026-05-06
**Release Date w/c 2026-08-31
*YP 5.0.18 Build Date 2026-04-27
 
*YP 5.0.18 Release Date 2026-05-13
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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"