Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(5 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Status 10 March 2026 ==
== Yocto Project Status 21 April 2026 ==
Current Dev Position: YP 6.0 M3<br/>
Current Dev Position: YP 6.0 M4<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>
Next Deadline: YP 6.0 M4 Build Date 2026-04-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 Apr. 23rd 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 Apr. 21st 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 Apr. 23rd 10am GMT and Monday Apr. 27th 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 5.0.17 was released
*YP 5.3.2 is due to be released
*YP 6.0 M3 was released
*YP 6.0 M2 is in QA
*YP 4.0.35 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M4 is due to build
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*We continue to triage the CVEs being reported by the new tooling.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.  
*Various fixes have merged or are planned to merge before the M4 release build:
*We have issues which need further work that will block M3:  
**Various CVE issue resolutions from CVE triage
**x86 kvm seemingly broken with certain CPU features (#16074)
**Reproducibility issues with strace/apr-util
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Make race in groff
**Failure to generate regression reports in release builds
**Shadow-native tallylog issue fix
*We also have issues we need to resolve before M3:
**Upgrade of barebox to align with an LTS release
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
**Splitting wic into an external tool.
**Sbom-cve-check upgrade (along with dependencies)
**Kernel rust support.
*Issues still pending:
**Switching to pkg-config.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**How to improve DEBUG_BUILD?
**Intermittent wic failures on the autobuilder
**DISTRO_FEATURES defaults improvements.
*At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them
**SBOM/cve-check changes.
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.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*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.
*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 final whinlatter build is happening this week.
*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 43:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2790 (last week 2777) (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: 1078 (last week 1072)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
'''YP 6.0 Milestone Dates:'''<br/>
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.16  is released.
*YP 5.0.17 was released.
*YP 5.3.2  is released.
*YP 4.0.35 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.4
*YP 5.3.3 Build Date 2026-03-16
**Build Date 2026-04-20  
*YP 5.3.3 Release Date 2026-04-01
**Release Date 2026-05-06
*YP 5.0.17 Build Date 2026-03-30
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20  
*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:47, 21 April 2026

Yocto Project Status 21 April 2026

Current Dev Position: YP 6.0 M4
Next Deadline: YP 6.0 M4 Build Date 2026-04-20

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.0.17 was released
  • YP 6.0 M3 was released
  • YP 4.0.35 is in QA
  • YP 6.0 M4 is due to build
  • We continue to triage the CVEs being reported by the new tooling.
  • Various fixes have merged or are planned to merge before the M4 release build:
    • Various CVE issue resolutions from CVE triage
    • Reproducibility issues with strace/apr-util
    • Make race in groff
    • Shadow-native tallylog issue fix
    • Upgrade of barebox to align with an LTS release
    • Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
    • Sbom-cve-check upgrade (along with dependencies)
  • Issues still pending:
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
    • Intermittent wic failures on the autobuilder
  • At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them

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.

  • 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.
  • The final whinlatter build is happening this week.

Ways to contribute:

New to the project?

Tracking Metrics:

Upcoming dot releases:

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=86807"