Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(249 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status January 3rd, 2023 ==
== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 4.2 M2<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: 23rd January 2023 YP 4.2 M2 Build<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 January 5th 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 January 3rd 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.2 M1 and YP 4.0.6 were released.
*YP 4.0.34 was released.
*Builds on the autobuilder are problematic at present due to connection losses with the controller machine. We understand the cause and will be migrating the controller to a new server/location in the next maintenance window to address this.
*YP 5.3.3 is approved for release.
*A number of invasive bitbake changes have merged including a change to add threading to bitbake’s server/cooker. This will allow us to attempt to resolve various UI/server hang related open bugs and to improve the user experience, e.g. Ctrl+C handling. If people do see issues with hangs, please report them and include the tail end of the bitbake-cookerdaemon.log file.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*The bitbake cache changes to optionally include more hash debugging information did merge. This currently triggers only for the bitbake -S operations but once that mode is triggered for memory resident bitbake, it is “sticky” and will remain set until it unloads. We have seen some OOM issues on autobuilder workers which may be related to this, more debugging is needed to check on bitbake’s memory usage.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Automatic bitbake function library dependency code has also merged and is active. This should let us migrate class code to become library code for performance improvements.
*Issues still pending:
*A bug in the layer.conf variable changes was identified which was causing re-parsing when it wasn’t necessary. A fix has been merged to address that.
**Splitting wic into an external tool.
*The OE TSC decided in favour of adding export flag expansion despite the performance impact so that patch will be queued.
**Converting scripts/run-cvecheck to sbom-cve-check
*We merged a number of neat rust improvements which add on target cargo support and added automated QA tests for this functionality so we can ensure it continues to work and doesn’t regress. Thanks Alex Kiernan, we hope to see more series like this one!
**DISTRO_FEATURES defaults improvements.
*CVE levels in master have improved but still need a little work
**RHEL 9 xattrs/selinux/tar issue
*The autobuilder maintenance window is moving from Friday to Monday.
**How to improve DEBUG_BUILD?
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
**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:'''<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: patchtest, layerindex, 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 4.2 See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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 https://docs.google.com/spreadsheets/d/e/2PACX-1vRgNISmH0Ditf0bRtSezeR2XsgKIiSFJKF6KJUHpnzocNGzvKZbuSDKfmV3n64BFXDRqElBSJnhHtG4/pubchart?oid=1993375488&format=interactive


'''YP 4.2 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.2 M1 is released
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.2 M2 build date 2023/01/23
*YP 4.2 M2 Release date 2023/02/03
*YP 4.2 M3 build date 2023/02/20
*YP 4.2 M3 Release date 2023/03/03
*YP 4.2 M4 build date 2023/04/03
*YP 4.2 M4 Release date 2023/04/28
 
'''Upcoming dot releases:'''<br/>
*YP 4.0.6 is released
*YP 4.1.2 build date 2023/01/09
*YP 4.1.2 Release date 2023/01/20
*YP 3.1.22 build date 2023/01/16
*YP 3.1.22 Release date 2023/01/27
*YP 4.0.7 build date 2023/01/30
*YP 4.0.7 Release date 2023/02/10
*YP 3.1.23 build date 2023/02/13
*YP 3.1.23 Release date 2023/02/24
*YP 4.0.8 build date 2023/02/27
*YP 4.0.8 Release date 2023/03/10
*YP 4.1.3 build date 2023/03/06
*YP 4.1.3 Release date 2023/03/17
*YP 3.1.24 build date 2023/03/20
*YP 3.1.24 Release date 2023/03/31
*YP 4.0.9 build date 2023/04/10
*YP 4.0.9 Release date 2023/04/21
*YP 4.1.4 build date 2023/05/01
*YP 4.1.4 Release date 2023/05/13
*YP 3.1.25 build date 2023/05/08
*YP 3.1.25 Release date 2023/05/19
*YP 4.0.10 build date 2023/05/15
*YP 4.0.10 Release date 2023/05/26


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2457 (last week 2452) (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: 1189 (last week 1188)
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 282 (24%) [last week 282 (24%)]
**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 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/>
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 74: Line 76:


== Archives ==
== Archives ==
*[[2026 Yocto Project Weekly Status Archive]]
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2022 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"