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 31 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 Apr. 2nd 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 31st 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 Apr. 2nd 10am GMT and Monday Apr. 6th 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 4.0.34 was released.
*YP 5.0.17 was released
*YP 5.3.3 is approved for release.
*YP 6.0 M3 was released
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 4.0.35 is in QA
*YP 6.0 M3 is now due to build however there are still key changes missing.
*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:
*Issues still pending:
**Splitting wic into an external tool.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Converting scripts/run-cvecheck to sbom-cve-check
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**DISTRO_FEATURES defaults improvements.
**Intermittent wic failures on the autobuilder
**RHEL 9 xattrs/selinux/tar issue
*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
**How to improve DEBUG_BUILD?
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.
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*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.
*Issues that are mostly known quantities still needing work:
*The final whinlatter build is happening this week.
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*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.
*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 43:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2814 (last week 2819) (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: 1062 (last week 1072)
**Total patches found: 1078 (last week 1072)
**Patches in the Pending State: 148 (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 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 4.0.34 was released.
*YP 5.0.17 was released.
*YP 5.3.3 ready for release.
*YP 4.0.35 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.3.4
*YP 5.0.17 Release Date 2026-04-15
**Build Date 2026-04-20
*YP 4.0.35 Build Date 2026-04-06
**Release Date 2026-05-06
*YP 4.0.35 Release Date 2026-04-22
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*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"