Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
== Yocto Project Status 21 April 2026 ==
== Yocto Project Status 11 August 2026 ==
Current Dev Position: YP 6.0 M4<br/>
Current Dev Position: YP 6.1 M3<br/>
Next Deadline: YP 6.0 Release Date w/c 2026-05-04<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 30th Apr. 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 29th Apr. 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 30th Apr. 10am GMT (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 4.0.35 is due to release
*YP 6.1 M2 has been released
*YP 5.3.4 is in QA
*YP 6.1 M3 is due in three weeks and this will be the feature freeze point for YP 6.1.
*YP 6.0 rc1 is in QA
*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.
*There will be no patch review on Monday 4th May due to public holidays.
*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 continue to triage the CVEs being reported by the new tooling.
*The NPM fetcher has been re-enabled in bitbake with security improvements and additional test cases
*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
*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.
*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
*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 have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
*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:
*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
**Matchbox-wm segfault/xserver restart
*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
**aarch64/x86-64 build host contamination/reproducibility issue
*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 but are trying to clear the backlog.
*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:'''<br/>
'''Ways to contribute:'''<br/>
Line 33: Line 37:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2788 (last week 2790) (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: 1085 (last week 1078)
**Total patches found: 1028 (last week 1029)
**Patches in the Pending State: 146 (13%) [last week 147 (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/>
*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:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.35 is in review.
*YP 6.0.3 due to release
*YP 5.3.4 is in QA
**Release Date w/c 2026-08-24
**Release Date 2026-05-06
*YP 5.0.20
*YP 5.0.18
**Build Date w/c 2026-08-17
**Build Date   2026-05-11
**Release Date w/c 2026-08-31
**Release Date 2026-05-25
 
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


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"