Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
 
(135 intermediate revisions by 3 users not shown)
Line 1: Line 1:
== Yocto Project Weekly Status June 13th, 2023 ==
== Yocto Project Weekly Status Mar. 11th, 2025 ==
Current Dev Position: YP 4.3 M2<br/>
Current Dev Position: YP 5.2 M4 - Feature Freeze<br/>
Next Deadline: 17th July 2023 YP 4.3 M2 build date<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 June 15th 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 June 13th 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.3 M1 has passed QA and is due to release
*YP 5.1.3 was released
*The 6.1 kernel continues to have stability issues which appear to be introduced between 6.1.26 and 6.1.28, we’ve not seen the issue so far with 6.1.27. We know it happens on 32 and 64 bit x86 and occurs even with just one CPU enabled. This has not been seen by other kernel users which is a concern too.
*YP 5.2 M3 is in QA
*We continue to see problematic intermittent failures on the autobuilder. We’re struggling to make progress against these and they are feeling overwhelming. We’re open to ideas on how we might try and address them. Experience shows that if left unresolved/ignored, people do end up hitting them in real world usage or during testing of their own products.
*YP 5.0.8 is ready for QA
*The autobuilder test matrix has seen some revisions:
*We are now at feature freeze for YP 5.2
**to split out toolchain testing to a separate target
*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.
**remove some duplicate testing for efficiency
*An infrastructure issue where git mirroring was stalling has been fixed
**optimize reproducibility testing to improve speed
*There continue to be 502 gateway errors on some services due to overload from bot activity. This is impacting the autobuilder as well.
We’re also about to add limited meta-clang testing to the test matrix.
*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.
These should improve autobuilder test execution time but has made one test race issue much more common which will need to be addressed.
*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:'''<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 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 4.2. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium.2B_4.2_Unassigned_Enhancements.2FBugs
*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 4.3 Milestone Dates:'''<br/>
'''Tracking Metrics:'''<br/>
*YP 4.3 M1 is ready for release
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*YP 4.3 M2 build date  2023/07/17
*OE-Core/Poky Patch Metrics
*YP 4.3 M2 Release date 2023/07/28
**Total patches found: 1027 (last week 1024)
*YP 4.3 M3 build date  2023/08/28
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*YP 4.3 M3 Release date 2023/09/08
*https://autobuilder.yocto.io/-release/patchmetrics/
*YP 4.3 M4 build date  2023/10/02
 
*YP 4.3 M4 Release date 2023/10/27
'''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 3.1.26 build date 2023/06/19
*YP 5.1.3 was released,
*YP 3.1.26 Release date 2023/06/30
*YP 5.0.8 is waiting for QA.
*YP 4.0.11 build date 2023/06/26
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.11 Release date 2023/07/07
*YP 5.1.4 Release Date 2025-04-04
*YP 4.2.2 build date 2023/07/10
*YP 4.0.26 Build Date 2025-04-07
*YP 4.2.2 Release date 2023/07/21
*YP 4.0.26 Release Date 2025-04-18
*YP 3.1.27 build date 2023/07/31
*YP 5.0.9 Build Date 2025-04-21
*YP 3.1.27 Release date 2023/08/11
*YP 5.0.9 Release Date 2025-05-02
*YP 4.0.12 build date 2023/08/07
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.12 Release date 2023/08/18
*YP 4.0.27 Release Date 2025-05-30
*YP 4.2.3 build date 2023/08/28
*YP 5.0.10 Build Date 2025-06-02
*YP 4.2.3 Release date 2023/09/08
*YP 5.0.10 Release Date 2025-06-13
*YP 3.1.28 build date 2023/09/18
*YP 4.0.28 Build Date 2025-06-30
*YP 3.1.28 Release date 2023/09/29
*YP 4.0.28 Release Date 2025-07-11
*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/>
*WDD 2524 (last week 2527) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1161 (last week 1162)
**Patches in the Pending State: 271 (23%) [last week 271 (23%)]
*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 76: Line 69:


== 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, 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

Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Weekly_Status&oldid=86582"