Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(158 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status August 15th, 2023 ==
== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 4.3 M3<br/>
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release<br/>
Next Deadline: 28th August 2023 YP 4.3 M3 build date<br/>
Next Deadline: YP 5.3 M4 Build Date 2025-11-10<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 Oct. 30th at 7:30 am PST (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 Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)
 
'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*We are now two weeks away from feature freeze for 4.3.
*YP 5.3 M3 is in QA
*YP 3.1.27 was released
*YP 5.0.13 is under review for release
*YP 4.0.12 is in QA.
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*The 6.4 kernel upgrade is still blocked as we’ve seen two nasty looking hangs in automated testing:
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/349/steps/12/logs/stdio
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
https://autobuilder.yoctoproject.org/typhoon/#/builders/148/builds/354/steps/12/logs/stdio
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
as well as a preempt-rt boot error that appears more consistently:
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
https://autobuilder.yoctoproject.org/typhoon/#/builders/72/builds/7616/steps/36/logs/stdio
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
The intermittent issues are a significant risk to automated testing stability and it is hard to know how to proceed as few people are willing/able to help with them. We’ve upgraded qemu 8.0.3 -> 8.0.4 just in case that helps.
**Help welcomed to resolve these issues!
The various systemd issues have mostly been resolved although the AUH did break as a result and will have to be fixed and rerun.
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
Build layout changed slightly with the removal of PE and PR from the WORKDIR path.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
There are patches pending which remove source control revisions from PV and move them to PKGV, further simplifying WORKDIR paths and generally improving the code and the way AUTOREV works. This allows SRCPV to be removed as it is no longer needed.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*Significant fixes were made to both the binutils and gcc testsuites which avoid many of the mips toolchain test failures. The failure counts are roughly the same (few hundred) for each architecture now resulting in ~3200 failures overall.
*There are now consistently ~200 ltp ‘controllers’ failures on both arm and x86 targets.
*A new uninative version was released to add some patches to patchelf to avoid bugs.
*A new test addition to oe-selftest caused another test to fail consistently on the autobuilder and this has been tracked down to one test corrupting the other if they run in the same TMPDIR. This only happens with specific parallelism settings where they happen to run together or with no parallelism.
*We continue to see intermittent ptest failures for glib-networking, mdadm and openssh, help would be much appreciated.
*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/


'''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!
*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!
*There are bugs identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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 bugs that are currently unassigned for YP 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*There are bugs identified as possible for newcomers to the project: https://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_Unassigned_Enhancements/Bugs
*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.
*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.
*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  
*Help us resolve CVE issues: CVE metrics  
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*We have a growing number of bugs in bugzilla, any help with them is appreciated.
*Ongoing project 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 as it will allow us to potentially find ways to fund specific work items.
'''Tracking Metrics:'''<br/>
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 4.3 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 4.3 M3 build date  2023/08/28
*YP 5.3 M3 is in QA.
*YP 4.3 M3 Release date 2023/09/08
*YP 5.3 M4 Build Date 2025-11-10
*YP 4.3 M4 build date  2023/10/02
*YP 5.3 M4 Release Date 2025-11-28
*YP 4.3 M4 Release date 2023/10/27


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 3.1.27 is released
*YP 5.0.13 is in review for release.
*YP 4.0.12 is in QA
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.12 Release date 2023/08/18
*YP 4.0.31 Release Date 2025-11-14
*YP 4.2.3 build date 2023/08/28
*YP 5.0.14 Build Date 2025-11-17
*YP 4.2.3 Release date 2023/09/08
*YP 5.0.14 Release Date 2025-11-28
*YP 3.1.28 build date 2023/09/18
*YP 4.0.32 Build Date 2025-12-15
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.32 Release Date 2025-12-24
*YP 4.0.13 build date 2023/09/25
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.13 Release date 2023/10/06
*YP 5.0.15 Release Date 2026-01-16
*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/>
*WDD 2463 (last week 2495) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1186 (last week 1186)
**Patches in the Pending State: 255 (22%) [last week 256 (22%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/


'''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 75: Line 62:


== Archives ==
== Archives ==
*[[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:50, 28 October 2025

Yocto Project Weekly Status Oct. 28th, 2025

Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release
Next Deadline: YP 5.3 M4 Build Date 2025-11-10

Next Team Meetings:

Project data dashboard: https://dashboard.yoctoproject.org/

Key Status/Updates:

  • YP 5.3 M3 is in QA
  • YP 5.0.13 is under review for release
  • Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
  • We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
    • check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
    • Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
    • The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
    • The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
    • Help welcomed to resolve these issues!
  • Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
  • “poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
  • There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

Ways to contribute:

Tracking Metrics:

YP 5.3 Milestone Dates:

  • YP 5.3 M3 is in QA.
  • YP 5.3 M4 Build Date 2025-11-10
  • YP 5.3 M4 Release Date 2025-11-28

Upcoming dot releases:

  • YP 5.0.13 is in review for release.
  • YP 4.0.31 Build Date 2025-11-03
  • YP 4.0.31 Release Date 2025-11-14
  • YP 5.0.14 Build Date 2025-11-17
  • YP 5.0.14 Release Date 2025-11-28
  • YP 4.0.32 Build Date 2025-12-15
  • YP 4.0.32 Release Date 2025-12-24
  • YP 5.0.15 Build Date 2026-01-05
  • YP 5.0.15 Release Date 2026-01-16

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