Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(36 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 11th, 2025 ==
== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<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 Mar. 13th at 7:30 am PST (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 Project Engineering Sync Tuesday Mar. 11th at 8 am PST (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/>
*YP 5.1.3 was released
*YP 5.3 M3 is in QA
*YP 5.2 M3 is in QA
*YP 5.0.13 is under review for release
*YP 5.0.8 is ready for QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We are now at feature freeze for YP 5.2
*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:
*We have a new dashboard index page linking to key tools/data pages within the project: https://dashboard.yoctoproject.org/ . Help on further improvements is welcome. We are aiming to drive the data from the autobuilder.
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
*An infrastructure issue where git mirroring was stalling has been fixed
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
*The buildbot workers display has been fixed to allow more builds to be shown and an autobuilder build scheduling issue has been resolved allowing better resource utilization.
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
*We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
**Help welcomed to resolve these issues!
*There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
*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.
*A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*Emails have been sent about the CVE/NVD situation proposing a path forward.
*The gomod mirror issue in meta-openembedded was continuing to give failed builds on the autobuilder.The patch has been reverted in meta-openembedded for now to regain stable builds. Warnings were creeping in whilst the error was masking them. We need to fix the root cause.
*Our own systemctl python script has been replaced with the correct tool for better compatibility
*We’ve identified a significant increase in build disk usage from the rust upgrade.


'''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!
*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 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 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 identified as possible for newcomers to the project: https://wiki.yoctoproject.org/wiki/Newcomers
*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.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.2_Unassigned_Enhancements/Bugs
*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.
Line 38: Line 36:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1027 (last week 1024)
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 5.3 Milestone Dates:'''<br/>
*YP 5.2 M3 in QA.
*YP 5.3 M3 is in QA.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.2 M4 Release Date 2025-04-25
*YP 5.3 M4 Release Date 2025-11-28


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.1.3 was released,
*YP 5.0.13 is in review for release.
*YP 5.0.8 is waiting for QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.31 Release Date 2025-11-14
*YP 5.1.4 Release Date 2025-04-04
*YP 5.0.14 Build Date 2025-11-17
*YP 4.0.26 Build Date 2025-04-07
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.32 Build Date 2025-12-15
*YP 5.0.9 Build Date 2025-04-21
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.9 Release Date 2025-05-02
*YP 5.0.15 Build Date 2026-01-05
*YP 4.0.27 Build Date 2025-05-19
*YP 5.0.15 Release Date 2026-01-16
*YP 4.0.27 Release Date 2025-05-30
*YP 5.0.10 Build Date 2025-06-02
*YP 5.0.10 Release Date 2025-06-13
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11


'''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/>

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"