Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(392 intermediate revisions by 6 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Aug. 24, 2021 ==
== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 3.4 M3<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: 23rd Aug. 2021 YP 3.4 M3 build (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 Aug. 26th at 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Monthly Project Meeting Tuesday Sept. 7th at 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Engineering Sync Tuesday Aug. 24th at 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)
*Twitch -  See https://www.twitch.tv/theyoctojester
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 3.1.10 was released
*YP 4.0.34 was released.
*Next week is feature freeze for YP 3.4
*YP 5.3.3 is approved for release.
*Known pending work for YP 3.4 includes rust support in core and the prserv changes.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*OE-Core has moved to the new override syntax and is now only compatible with the honister release series. Other layers will need to migrate to the new syntax to work with it. There is documentation about handling migration to the new syntax in the migration section of the manual:
*YP 6.0 M3 is now due to build however there are still key changes missing.  
http://docs.yoctoproject.org/migration-guides/migration-3.4.html#override-syntax-changes
*Issues still pending:
*There continue to be small bug fixes from the override syntax change but most of the core layers tested on the autobuilder now seem to be working ok.
**Splitting wic into an external tool.
*We merged the upgrade to glibc to 2.34. Unfortunately this version makes some changes which have broken uninative and pseudo. Fixes for those issues are being investigated.  
**Converting scripts/run-cvecheck to sbom-cve-check
*Kernel changes to drop 5.4 and switch to 5.10 and 5.13 are pending, mainly on other layers being ready for the change to the default versions.
**DISTRO_FEATURES defaults improvements.
*There also appear to be issues in the buildtools tarball on aarch64, probably from the gcc 11 upgrade.
**RHEL 9 xattrs/selinux/tar issue
*There is a plan to migrate the tune files into architecture specific directories. This patch will likely merge in the next few days and will need BSP layers to be updated as the tune files will no longer be found.
**How to improve DEBUG_BUILD?
*The bitbake fetcher no longer ignores SSL certificates by default (this wasn’t a huge problem as we separately checksum input files).
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*LTO linker flags handling changes were merged now the reproducibility issues it introduced were fixed meaning LTO builds should be more reproducible.
*Issues that are mostly known quantities still needing work:
*Overlayfs class changes were merged.
**x86 kvm seemingly broken with certain CPU features (#16074)
*Intermittent issues are ongoing and help is very much welcome on these 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
**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/>
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 that are currently unassigned for YP 3.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_3.3_Unassigned_Enhancements.2FBugs
*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/
*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.
*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.
*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing
 
'''New to the project?'''<br/>
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER


'''YP 3.4 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 3.4 M3 build date 2021/08/23
*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 3.4 M3 Release date 2021/09/03
*OE-Core/Poky Patch Metrics
*YP 3.4 M4 build date 2021/10/04
**Total patches found: 1062 (last week 1072)
*YP 3.4 M4 Release date 2021/10/29
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/


'''Planned upcoming dot releases:'''<br/>
'''YP 6.0 Milestone Dates:'''<br/>
*YP 3.1.11 build date 2021/09/13
*YP 6.0 M3 Build Date 2026-03-23
*YP 3.1.11 release date 2021/9/24
*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


'''Tracking Metrics:'''<br/>
'''Upcoming dot releases:'''<br/>
*WDD 2610 (last week 2583) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.0.34 was released.
*Poky Patch Metrics 
*YP 5.3.3 ready for release.
**Total patches found: 1299 (last week 1293)
*YP 5.0.17 Build Date 2026-03-30
**Patches in the Pending State: 484 (37%) [last week 485 (38%)]
*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 50: 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]]
*[[2022 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2021 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2020 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2019 Yocto Project Weekly Status Archive]]
*[[2018 Yocto Project Weekly Status Archive]]
*[[2018 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