Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(189 intermediate revisions by 5 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 15th, 2023 ==
== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 4.3 M3<br/>
Current Dev Position: YP 6.0 M3<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<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 August 17th 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday August 15th 8 am PDT (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 4.3 M2 was released.
*YP 5.3.3 was released.
*YP 3.1.27 was rebuilt after a toolchain tests fix and is in QA
*YP 5.0.17 is in QA
*YP 4.0.12 rc1 was built but will need to be rebuilt due to an autobuilder failure due to certificate expiration.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*The merged systemd upgrade has destablised the autobuilder. We don’t want to revert the upgrade but the regressions are causing multiple test failures and this along with other issues in multiple patch series means patch merging is effectively stalled.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*There are two issues blocking the 6.4 kernel upgrade, one is qemuarm drm boot errors and the second is broken networking for systemd images under qemu.
*Issues with pending work needed:
*Support for a  new recipe sanity testing task (do_recipe_qa) was merged and there is a hope/plan to move more “processing” operations over to this task to improve general parsing time.
**Converting scripts/run-cvecheck to sbom-cve-check
*CVE metrics are worrying with significant numbers of open CVEs against master, many of them kernel related. The 6.4 upgrade should help but that is blocked. Mickledore is also badly affected with a record high count. https://autobuilder.yocto.io/pub/non-release/patchmetrics/
**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:'''<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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.


'''YP 4.3 Milestone Dates:'''<br/>
'''New to the project?'''<br/>
*YP 4.3 M3 build date  2023/08/28
*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER
*YP 4.3 M3 Release date 2023/09/08
*YP 4.3 M4 build date  2023/10/02
*YP 4.3 M4 Release date 2023/10/27
 
'''Upcoming dot releases:'''<br/>
*YP 3.1.27 is released
*YP 4.0.12 is in QA
*YP 4.0.12 Release date 2023/08/18
*YP 4.2.3 build date 2023/08/28
*YP 4.2.3 Release date 2023/09/08
*YP 3.1.28 build date 2023/09/18
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.13 build date 2023/09/25
*YP 4.0.13 Release date 2023/10/06
*YP 3.1.29 build date 2023/10/30
*YP 3.1.29 Release date 2023/11/10
*YP 4.0.14 build date 2023/11/06
*YP 4.0.14 Release date 2023/11/17
*YP 4.2.4 build date 2023/11/13
*YP 4.2.4 Release date 2023/11/24
*YP 3.1.30 build date 2023/12/11
*YP 3.1.30 Release date 2023/12/22
*YP 4.0.15 build date 2023/12/18
*YP 4.0.15 Release date 2023/12/29


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2463 (last week 2495) (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: 1186 (last week 1186)
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 255 (22%) [last week 256 (22%)]
**Patches in the Pending State: 148 (14%) [last week 148 (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 5.3.3 was released.
*YP 5.0.17 is in QA.
*YP 4.0.35
**Build Date 2026-04-06
**Release Date 2026-04-22
*YP 5.3.4
**Build Date  2026-04-20
**Release Date 2026-05-06
*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar


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


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