Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status Mar. 11th, 2025 ==
== Yocto Project Weekly Status Mar. 25th, 2025 ==
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<br/>
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze<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 Mar. 27th 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 Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 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.2 M3 is due to be released
*YP 5.2 M3 is in QA
*YP 5.0.8 is due to be released
*YP 5.0.8 is ready for QA
*YP 5.1.4 is in QA
*We are now at feature freeze for YP 5.2
*We are at feature freeze for YP 5.2 with our first rc build next week
*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.
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*An infrastructure issue where git mirroring was stalling has been fixed
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
*SRC_URI entries for git now support tag verification against a specified source revision
*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.
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.
*Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
*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/>
Line 38: Line 35:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2801 (last week 2786) (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: 1060 (last week 1049)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.2 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.2 M3 in QA.
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 5.1.3 was released,
*YP 5.0.8 is ready for release.
*YP 5.0.8 is waiting for QA.
*YP 5.1.4 is in QA.
*YP 5.1.4 Build Date 2025-03-24
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.26 Release Date 2025-04-18

Revision as of 14:46, 25 March 2025

Yocto Project Weekly Status Mar. 25th, 2025

Current Dev Position: YP 5.2 M4 - Feature Freeze
Next Deadline: YP 5.2 M4 Build Date 2025-03-31 - Feature Freeze

Next Team Meetings:

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

Key Status/Updates:

  • YP 5.2 M3 is due to be released
  • YP 5.0.8 is due to be released
  • YP 5.1.4 is in QA
  • We are at feature freeze for YP 5.2 with our first rc build next week
  • We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
  • The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
  • SRC_URI entries for git now support tag verification against a specified source revision
  • Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
  • Kernel stable updates merged including a key qemumips fix and various CVE fixes.
  • A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
  • We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

Ways to contribute:

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M3 is ready for release.
  • YP 5.2 M4 Build Date 2025-03-31
  • YP 5.2 M4 Release Date 2025-04-25

Upcoming dot releases:

  • YP 5.0.8 is ready for release.
  • YP 5.1.4 is in QA.
  • YP 4.0.26 Build Date 2025-04-07
  • YP 4.0.26 Release Date 2025-04-18
  • YP 5.0.9 Build Date 2025-04-21
  • YP 5.0.9 Release Date 2025-05-02
  • YP 4.0.27 Build Date 2025-05-19
  • 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:
https://wiki.yoctoproject.org/wiki/TSC

Archives