Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(64 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status April 2nd, 2024 ==
== Yocto Project Weekly Status Mar. 11th, 2025 ==
Current Dev Position: YP 5.0 M4 - Final Release <br/>
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Next Deadline: 1st April 2024 YP 5.0 M4 build<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 April 4th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday April 2nd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Mar. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch -  See https://www.twitch.tv/theyoctojester
*Twitch -  See https://www.twitch.tv/theyoctojester  


'''Key Status/Updates:'''<br/>
'''Key Status/Updates:'''<br/>
*YP 4.0.17 has been released.
*YP 5.1.3 was released
*YP 4.3.4 is in QA and is the final planned nanbield release.
*YP 5.2 M3 is in QA
*YP 5.0 rc1 is now due to build when ready.
*YP 5.0.8 is ready for QA
*Steve is taking patches for Dunfell until around April 8 in preparation for an April 15 build. This will be the last release of dunfell.
*We are now at feature freeze for YP 5.2
*5.0 build status:
*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.
**The opkg lock issue has been worked around for now in the run-postinsts script
*An infrastructure issue where git mirroring was stalling has been fixed
**An intermittent oe-selftest failure (sstatetests hang) was tracked down to a race in tinfoil event handling.
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
**The public hash equivalence server changes aren’t ready yet unfortunately
*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.
**There are issues with the size of the buildhistory repository which is being split up, this needs to happen before we can build the release.
*We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
**A key worry now is the documentation for the release, especially given it is an LTS. There are emails on the docs list about this, help is much appreciated. This will now be the main delay on the release timeframe.
*There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
*A new yocto-status https://lists.yoctoproject.org/g/yocto-status/topics mailing list has been created where we plan to send just the project weekly status reports and any other suitable updates on the project. This should help those who found the traffic of the other mailing lists too much.
*A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
*A yocto-patches https://lists.yoctoproject.org/g/yocto-patches/topics mailing list has been setup and patches that used to go to the yocto@ list will be migrating over to this new list, making yocto@ a bit more friendly for questions and discussions.
*Fitimage and u-boot tests were reworked and rationalized which was long overdue, thanks Adrian.
*Some other obsolete mailing lists were removed or made read-only to try and make it easier for people to find the right place to see/send things.
*Emails have been sent about the CVE/NVD situation proposing a path forward.
*Debian 12 and Fedora 40 containers have been added to crops (Thanks Rob Wolley)
*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.
*All the crops yocto-base containers now include python3-virtualenv
*Our own systemctl python script has been replaced with the correct tool for better compatibility
*The “Binary Distro” work is now well underway and there are PR Server passthrough patches ready for review. The wiki page https://wiki.yoctoproject.org/wiki/Binary_Distro_Prototype#Policies_and_Processes has had a number of policy/process proposals documented, at least as a first pass. Help is welcome to help improve these, or highlight where further documentation is needed.
*We’ve identified a significant increase in build disk usage from the rust upgrade.
*One year after the original linux.com article, an update was published: https://www.yoctoproject.org/blog/2024/03/28/maintainer-confidential-challenges-and-opportunities-one-year-on/
*There was a significant security issue with xz release tarballs. We never merged the affected version and it was never in any of our main branches but we did test it on the autobuilder and saw build failures. We continue to watch for information on any potential implications of that. We have removed the compromised tarballs from our mirrors.
*We continue to watch the NIST NVD (CVE database) situation, the recent update didn’t clarify much. Unfortunately there doesn’t appear to be a clear path forward as yet.


'''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 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://wiki.yoctoproject.org/wiki/Newcomers
*There are bugs that are currently unassigned for YP 5.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.0_Unassigned_Enhancements/Bugs
*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
*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.


'''YP 5.0 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 5.0 M4 build date  2024/04/01
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0 M4 Release date 2024/04/30
*OE-Core/Poky Patch Metrics
**Total patches found: 1027 (last week 1024)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/
 
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.2 M3 in QA.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.17 is released.
*YP 5.1.3 was released,
*YP 4.3.4 is in QA.
*YP 5.0.8 is waiting for QA.
*YP 3.1.33 build date 2024/04/15
*YP 5.1.4 Build Date 2025-03-24
*YP 3.1.33 Release date 2024/04/26
*YP 5.1.4 Release Date 2025-04-04
*YP 4.0.18 build date 2024/04/22
*YP 4.0.26 Build Date 2025-04-07
*YP 4.0.18 Release date 2024/05/03
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.19 build date 2024/06/03
*YP 5.0.9 Build Date 2025-04-21
*YP 4.0.19 Release date 2024/06/14
*YP 5.0.9 Release Date 2025-05-02
 
*YP 4.0.27 Build Date 2025-05-19
'''Tracking Metrics:'''<br/>
*YP 4.0.27 Release Date 2025-05-30
*WDD 2681 (last week 2703) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 5.0.10 Build Date 2025-06-02
*OE-Core/Poky Patch Metrics
*YP 5.0.10 Release Date 2025-06-13
**Total patches found: 1173 (last week 1156)
*YP 4.0.28 Build Date 2025-06-30
**Patches in the Pending State: 249 (21%) [last week 249 (22%)]
*YP 4.0.28 Release Date 2025-07-11
*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 63: Line 69:


== Archives ==
== Archives ==
*[[2025 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2024 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]
*[[2023 Yocto Project Weekly Status Archive]]

Latest revision as of 14:50, 11 March 2025

Yocto Project Weekly Status Mar. 11th, 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:

Key Status/Updates:

  • YP 5.1.3 was released
  • YP 5.2 M3 is in QA
  • YP 5.0.8 is ready for QA
  • We are now at feature freeze for YP 5.2
  • 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.
  • An infrastructure issue where git mirroring was stalling has been fixed
  • There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
  • 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.
  • We now have gitstats, SANITY_TESTED_DISTROS validation, toaster fixtures validation and wider use of central releases information within the autobuilder.
  • There have been improvements to the SPDX generation but these appear to have caused a significant performance regression which is being investigated.
  • A cause of intermittent failures from a python warning has been worked around and a small race fix for bitbake was also merged.
  • 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:

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M3 in QA.
  • YP 5.2 M4 Build Date 2025-03-31
  • YP 5.2 M4 Release Date 2025-04-25

Upcoming dot releases:

  • YP 5.1.3 was released,
  • YP 5.0.8 is waiting for 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 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