Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(116 intermediate revisions by 4 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 11th, 2024 ==
== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 5.1 M2 <br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: YP 5.1 M2 Build 8 July 2024<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 June 13th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday June 11th at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 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 4.0.19 is in QA
*YP 4.0.34 was released.
*YP 5.1 M1 rc1 is building
*YP 5.3.3 is approved for release.
*We identified the performance problem in bitbake using hash equivalence servers and have made changes to batch queries and improve build times
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*Extra logging for that performance problem is available by setting BB_LOGCONFIG=XXX/bitbake/contrib/autobuilderlog.json (the more verbose logging the autobuilder uses) which will then show if initial query or rehash looping takes longer than 30s for iterations or 60s overall.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*We changed locked-sigs to include the hash equivalence mapping data, removing the need to copy the cache file.
*Issues still pending:
*Libtool was upgraded to the 2.5.0 alpha release, many patches were merged upstream.
**Splitting wic into an external tool.
*Qemu has been upgraded to 9.0.0, kernel headers to 6.9 and stable and dev kernel updates merged (to 6.6.32)
**Converting scripts/run-cvecheck to sbom-cve-check
*There is one remaining issue on fedora40, systemtap-native does not build. The other Fedora 40 are believed to be fixed.
**DISTRO_FEATURES defaults improvements.
*Some layers are setting fallbacks for UNPACKDIR which break OE-Core by trying to claim compatibility with everything. Errors have been added to make this problem clear.
**RHEL 9 xattrs/selinux/tar issue
*sstate has had changes to fix a bug where build-history data was inconsistent. The siteconfig class was removed to make that change easier and improve the code, it was mostly unused anyway.
**How to improve DEBUG_BUILD?
*The parallelism in the hash client was removed as batching queries is much more effective and easier on the server.
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*There is an open letter the project has created related to the CVE/NVD situation, more information is available here: https://lists.openembedded.org/g/openembedded-architecture/message/1990
*Issues that are mostly known quantities still needing work:
*Please consider signing this to show support for those changes.
**x86 kvm seemingly broken with certain CPU features (#16074)
*Signatures from small businesses/consultancies are as welcome as those from larger organizations as we want to demonstrate the breadth of the need for these changes.
**Failure to generate regression reports in release builds
*There is a further update from Marta/Syslinbit on the CVE tooling/patches
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*We continue to have trouble tracking down the rust reproducibility problem in rustdoc.
*Issues that were resolved this week:
*Post release upgrading is resulting in an improvement in patch metrics which is great to see, more should appear next week in the statistics too.
**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/>
*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 are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 5.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_Unassigned_Enhancements/Bugs
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
*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.
 
*Help us resolve CVE issues: CVE metrics
'''New to the project?'''<br/>
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2774 (last week 2772) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1098)
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 205 (19%) [last week 205 (19%)]
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 5.1 M1 is in QA
*YP 6.0 M3 Build Date 2026-03-23
*YP 5.1 M1 Release date 2024-05-31
*YP 6.0 M3 Release Date 2026-04-08
*YP 5.1 M2 Build date 2024-07-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 5.1 M2 Release date 2024-07-19
*YP 6.0 M4 Release Date 2026-05-04
*YP 5.1 M3 Build date 2024-08-26
*YP 5.1 M3 Release date 2024-09-06
*YP 5.1 M4 Build date 2024-09-30
*YP 5.1 M4 Release date 2024-10-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.19 is ready for release.
*YP 4.0.34 was released.
*YP 5.0.2 Build Date 2024-06-24
*YP 5.3.3 ready for release.
*YP 5.0.2 Release Date 2024-07-05
*YP 5.0.17 Build Date 2026-03-30
*YP 4.0.20 Build Date 2024-07-15
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.20 Release Date 2024-07-26
*YP 4.0.35 Build Date 2026-04-06
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.35 Release Date 2026-04-22
*YP 5.0.3 Release Date 2024-08-23
*YP 5.3.4 Build Date 2026-04-20
*YP 4.0.21 Build Date 2024-09-09
*YP 5.3.4 Release Date 2026-05-06
*YP 4.0.21 Release Date 2024-09-20
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.4 Release Date 2024-10-04
*YP 5.0.19 Build Date 2026-05-26
*YP 4.0.22 Build Date 2024-10-14
*YP 5.0.19 Release Date 2026-06-05
*YP 4.0.22 Release Date 2024-10-25
*YP 5.0.5 Build Date 2024-11-11
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.23 Build Date 2024-11-18
*YP 4.0.23 Release Date 2024-11-29


'''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 76: Line 76:


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

Latest revision as of 14:48, 31 March 2026

Yocto Project Status 31 March 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 4.0.34 was released.
  • YP 5.3.3 is approved for release.
  • 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 still pending:
    • Splitting wic into an external tool.
    • Converting scripts/run-cvecheck to sbom-cve-check
    • DISTRO_FEATURES defaults improvements.
    • RHEL 9 xattrs/selinux/tar issue
    • How to improve DEBUG_BUILD?
    • RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
  • Issues that are mostly known quantities still needing work:
    • 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:

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:

  • YP 4.0.34 was released.
  • YP 5.3.3 ready for release.
  • YP 5.0.17 Build Date 2026-03-30
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86796"