Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Status 21 July 2026 ==
== Yocto Project Status 11 August 2026 ==
Current Dev Position: YP 6.1 M2<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>
Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday 13rd Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync  - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync  - Tuesday 11th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
*Yocto Project Patch Review - Thursday 13rd Aug. 10am GMT and Monday 17th Aug. 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 6.0.2 has been released
*YP 6.1 M2 has been released
*YP 5.0.19 is due to release
*YP 6.1 M3 is due in three weeks and this will be the feature freeze point for YP 6.1.
*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
*Some invasive LICENSE changes have merged into master:
*Alex Stewart is stepping down as maintainer of opkg - huge thanks to him for his work on the project over the last 5 years, and thanks to National Instruments/Emerson for their continued support of opkg. Maintainership is being handed over to Erick Shepherd (also from NI/Emerson), there is also a call for input and anyone interested in being a co-maintainer: https://lists.yoctoproject.org/g/opkg/topic/120687514
**We now require the LICENSE field to match SPDX identifiers.
*The NPM fetcher has been re-enabled in bitbake with security improvements and additional test cases
**The build will issue warnings when this isn’t the case.
*The upgrade to sbom-cve-check 1.3.3 has more correct handling of Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS assignments. The fallout in OE-core has been handled, other layers may see an uptick in reported CVEs.
**Non SPDX licenses will need to be of the form LicenseRef-XXX
*The SDK_TOOLCHAIN_LANGS variable has been replaced with a more general SDK_FEATURES variable to support improved SDK configurability. Uses of the old variable will need to be updated, `go` and `rust` langs are still supported as SDK features.
**CLOSED is no longer a valid value.  
*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
**‘WITH’ license exceptions are now supported
**Matchbox-wm segfault/xserver restart
Big thanks for Joshua for getting us to the point where we can finally clean this up!
**aarch64/x86-64 build host contamination/reproducibility issue
*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
*We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
Remaining intermittent build failures of concern:
*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.
**other qemu ‘hang’ type issues on ARM
*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
**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
**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:'''<br/>
'''Ways to contribute:'''<br/>
Line 44: Line 37:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2694 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1019 (last week 1019+)
**Total patches found: 1028 (last week 1029)
**Patches in the Pending State: 144 (14%) [last week 145 (14%)]
**Patches in the Pending State: 139 (14%) [last week 141 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Upcoming development releases:'''<br/>
'''Upcoming development releases:'''<br/>
*6.1 M2:
*6.1 M2: was released.
**Build Date: w/c 2026-07-20
**Release Date: w/c 2026-08-03
*6.1 M3:
*6.1 M3:
**Build Date: w/c 2026-08-31
**Build Date: w/c 2026-08-31
Line 62: Line 53:


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.19 due to release
*YP 6.0.3 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
**Release Date w/c 2026-08-24
*YP 5.0.20
*YP 5.0.20

Revision as of 14:46, 11 August 2026

Yocto Project Status 11 August 2026

Current Dev Position: YP 6.1 M3
Next Deadline: YP 6.1 M3: w/c 2026-08-31

Next Team Meetings:

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

Key Status/Updates:

  • YP 6.1 M2 has been released
  • YP 6.1 M3 is due in three weeks and this will be the feature freeze point for YP 6.1.
  • We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
  • Alex Stewart is stepping down as maintainer of opkg - huge thanks to him for his work on the project over the last 5 years, and thanks to National Instruments/Emerson for their continued support of opkg. Maintainership is being handed over to Erick Shepherd (also from NI/Emerson), there is also a call for input and anyone interested in being a co-maintainer: https://lists.yoctoproject.org/g/opkg/topic/120687514
  • The NPM fetcher has been re-enabled in bitbake with security improvements and additional test cases
  • The upgrade to sbom-cve-check 1.3.3 has more correct handling of Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS assignments. The fallout in OE-core has been handled, other layers may see an uptick in reported CVEs.
  • The SDK_TOOLCHAIN_LANGS variable has been replaced with a more general SDK_FEATURES variable to support improved SDK configurability. Uses of the old variable will need to be updated, `go` and `rust` langs are still supported as SDK features.
  • There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
    • Matchbox-wm segfault/xserver restart
    • aarch64/x86-64 build host contamination/reproducibility issue
  • We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.

Remaining intermittent build failures of concern:

    • other qemu ‘hang’ type issues on ARM
    • sometimes yocto-check-layer is showing checksum mismatch issues
    • intermittent ptest failures in many recipes

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming development releases:

  • 6.1 M2: was released.
  • 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 6.0.3 due to release
    • 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=86864"