Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(71 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Feb. 11th, 2025 ==
== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 5.2 M3<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 5.2 M3 Build date 2025-03-03<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 Feb. 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 Feb. 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.2 M2 was released
*YP 5.3.3 was released.
*YP 5.0.7 is under review and passed QA
*YP 5.0.17 is in QA
*We are now 3 weeks from feature freeze for 5.2
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*The project autobuilder has upgraded the controller to buildbot 4.2 which was tricky due to our custom plugin and changes to the framework used for the UI. The new UI should have the same functionality and seems faster and easier to use in places.
*YP 6.0 M3 is now due to build however there are still key changes missing.  
*We’d like to request help to process the open github pull requests for openembedded-core and bitbake:
*Issues with pending work needed:
**https://github.com/openembedded/openembedded-core/pulls
**Converting scripts/run-cvecheck to sbom-cve-check
**https://github.com/openembedded/bitbake/pulls
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
*Having these open doesn’t look good for the projects and we can’t disable them, some have been open for a long time. We did already clean up the poky pull requests.
**Failure to generate regression reports in release builds (need tags)
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
**Ubuntu 26.04 support (need worker adding for testing)
*There are multiple occasional but annoying autobuilder failures we could do with help debugging/fixing, summarized by https://valkyrie.yocto.io/pub/non-release/abint/ :
*Issues that have patches ready to merge:
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
**DISTRO_FEATURES defaults improvements.
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
**Fixing yocto-check-layer to work with --machines
***https://bugzilla.yoctoproject.org/show_bug.cgi?id=15463
**RHEL 9 xattrs/selinux/tar issue
**dnf failures in where ssh appears to fail, usually on qemumips but also seen on qemuarm: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13674
**Splitting wic into an external tool.
**Ongoing CDN failures
**RHEL 10/openSUSE Leap 16.0 support
**New memory allocation issues hinting we may need to scale builds back
*Issues that need investigation
*We are open to help developing patches to help debug issue further or other ideas on the causes and/or ways to mitigate them
**Reports of pseudo errors on Fedora 44 beta
*The Linux Foundation published information on navigating global regulations and sanctions: https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
*Please contact TSC members if there are questions/concerns.
*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 gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*Gold linker support was removed from core.
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp
*Linux 6.6 was removed so we now just have the 6.12 kernel we plan to release YP 5.2 with.
*The performance metric charts were improved to be able to show both commit based and time based data, allowing performance changes to be isolated more easily.
*The triage team decided to clear out the “newcomer” bugs in bugzilla since the remaining ones were likely too hard without specialist knowledge. We’d love to see new/realist newcomer bugs being added.
*The 5.2 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, thanks to all who have contributed so far!


'''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.


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2711 (last week 2704) (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: 1025 (last week 1029)
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 172 (17%) [last week 173 (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 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 5.2 M3 Build Date 2025-03-03
*YP 6.0 M3 Release Date 2026-04-08
*YP 5.2 M3 Release Date 2025-03-14
*YP 6.0 M4 Build Date 2026-04-13
*YP 5.2 M4 Build Date 2025-03-31
*YP 6.0 M4 Release Date 2026-05-04
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.0.7 is in review.
*YP 5.3.3 was released.
*YP 4.0.25 Build Date 2025-02-17
*YP 5.0.17 is in QA.
*YP 4.0.25 Release Date 2025-02-28
*YP 4.0.35
*YP 5.1.3 Build Date 2025-02-24
**Build Date 2026-04-06
*YP 5.1.3 Release Date 2025-03-07
**Release Date 2026-04-22
*YP 5.0.8 Build Date 2025-03-10
*YP 5.3.4
*YP 5.0.8 Release Date 2025-03-21
**Build Date 2026-04-20
*YP 5.1.4 Build Date 2025-03-24
**Release Date 2026-05-06
*YP 5.1.4 Release Date 2025-04-04
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Release Date 2025-04-18
*YP 5.0.9 Build Date 2025-04-21
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.27 Build Date 2025-05-19
*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 85: 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"