Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(66 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 11th, 2025 ==
== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<br/>
Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 5.1.3 was released
*YP 5.3.3 was released.
*YP 5.2 M3 is in QA
*YP 5.0.17 is in QA
*YP 5.0.8 is ready for QA
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*We are now at feature freeze for YP 5.2
*YP 6.0 M3 is now due to build however there are still key changes missing.  
*We have a new dashboard index page linking to key tools/data pages within the project: https://dashboard.yoctoproject.org/ . Help on further improvements is welcome. We are aiming to drive the data from the autobuilder.
*Issues with pending work needed:
*An infrastructure issue where git mirroring was stalling has been fixed
**Converting scripts/run-cvecheck to sbom-cve-check
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*The buildbot workers display has been fixed to allow more builds to be shown and an autobuilder build scheduling issue has been resolved allowing better resource utilization.
**Failure to generate regression reports in release builds (need tags)
*We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
**Ubuntu 26.04 support (need worker adding for testing)
*There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
*Issues that have patches ready to merge:
*A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
**DISTRO_FEATURES defaults improvements.
*Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
**Fixing yocto-check-layer to work with --machines
*Emails have been sent about the CVE/NVD situation proposing a path forward.
**RHEL 9 xattrs/selinux/tar issue
*The gomod mirror issue in meta-openembedded was continuing to give failed builds on the autobuilder.The patch has been reverted in meta-openembedded for now to regain stable builds. Warnings were creeping in whilst the error was masking them. We need to fix the root cause.
**Splitting wic into an external tool.
*Our own systemctl python script has been replaced with the correct tool for better compatibility
**RHEL 10/openSUSE Leap 16.0 support
*We’ve identified a significant increase in build disk usage from the rust upgrade.
*Issues that need investigation
**Reports of pseudo errors on Fedora 44 beta
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
*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.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp


'''Ways to contribute:'''<br/>
'''Ways to contribute:'''<br/>
*As people are likely aware, the project has a number of components which are either unmaintained, or have people with little to no time trying to keep them alive. These components include: devtool, toaster, wic, oeqa, autobuilder, CROPs containers, pseudo and more. Many have open bugs. Help is welcome in trying to better look after these components!
*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
*There is an issue open upstream with the openssl project related to making path relocation of openssl easier (as used in our buildtools tarball and SDK). We’d love assistance in moving this forward and getting some kind of upstream feature merged to make this easier: https://github.com/openssl/openssl/pull/19260
*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
*There are bugs that are currently unassigned for YP 5.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*We’d welcome new maintainers for recipes in OE-Core. Please see the list at: http://git.yoctoproject.org/cgit.cgi/poky/tree/meta/conf/distro/include/maintainers.inc and discuss with the existing maintainer, or ask on the OE-Core mailing list. We will likely move a chunk of these to “Unassigned” soon to help facilitate this.
 
*Help is very much welcome in trying to resolve our autobuilder intermittent issues. You can see the list of failures we’re continuing to see by searching for the “AB-INT” tag in bugzilla: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=AB-INT.
'''New to the project?'''<br/>
*Help us resolve CVE issues: CVE metrics
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project development plans are being developed in this document: https://docs.google.com/document/d/1xsnN_HcaMhqg6Dn1P_19AnumDaUMQSdFZ_I4rjD830A/edit?usp=sharing We need to continue to develop this as it will allow us to potentially find ways to fund specific work items.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1027 (last week 1024)
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.2 M3 in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 5.2 M4 Build Date 2025-03-31
*YP 6.0 M3 Release Date 2026-04-08
*YP 5.2 M4 Release Date 2025-04-25
*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.1.3 was released,
*YP 5.3.3 was released.
*YP 5.0.8 is waiting for QA.
*YP 5.0.17 is in QA.
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.35
*YP 5.1.4 Release Date 2025-04-04
**Build Date 2026-04-06
*YP 4.0.26 Build Date 2025-04-07
**Release Date 2026-04-22
*YP 4.0.26 Release Date 2025-04-18
*YP 5.3.4
*YP 5.0.9 Build Date 2025-04-21
**Build Date 2026-04-20
*YP 5.0.9 Release Date 2025-05-02
**Release Date 2026-05-06
*YP 4.0.27 Build Date 2025-05-19
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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/>
Line 69: Line 70:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]

Latest revision as of 14:44, 7 April 2026

Yocto Project Status 7 April 2026

Current Dev Position: YP 6.0 M3
Next Deadline: YP 6.0 M3 Build Date 2026-03-23

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.3.3 was released.
  • YP 5.0.17 is in QA
  • YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
  • YP 6.0 M3 is now due to build however there are still key changes missing.
  • Issues with pending work needed:
    • Converting scripts/run-cvecheck to sbom-cve-check
    • 32bit x86 kvm seemingly broken with certain CPU features (#16074)
    • Failure to generate regression reports in release builds (need tags)
    • Ubuntu 26.04 support (need worker adding for testing)
  • Issues that have patches ready to merge:
    • DISTRO_FEATURES defaults improvements.
    • Fixing yocto-check-layer to work with --machines
    • RHEL 9 xattrs/selinux/tar issue
    • Splitting wic into an external tool.
    • RHEL 10/openSUSE Leap 16.0 support
  • Issues that need investigation
    • Reports of pseudo errors on Fedora 44 beta
  • The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
  • 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.
  • We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
  • The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp

Ways to contribute:

New to the project?

Tracking Metrics:

YP 6.0 Milestone Dates:

  • 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:

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