Weekly Status: Difference between revisions

From Yocto Project
Jump to navigationJump to search
(34 intermediate revisions by the same user not shown)
Line 1: Line 1:
== Yocto Project Weekly Status July 23rd, 2024 ==
== Yocto Project Weekly Status Feb. 11th, 2025 ==
Current Dev Position: YP 5.1 M3 <br/>
Current Dev Position: YP 5.2 M3<br/>
Next Deadline: YP 5.1 M3 Build 26 Aug. 2024<br/>
Next Deadline: YP 5.2 M3 Build date 2025-03-03<br/>


'''Next Team Meetings:'''<br/>
'''Next Team Meetings:'''<br/>
*Bug Triage meeting Thursday July 25th at 7:30 am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Engineering Sync Tuesday July 23rd at 8 am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Weekly Project Engineering Sync Tuesday Feb. 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.20 is due to be released
*YP 5.2 M2 was released
*YP 5.1 M2 is in QA
*YP 5.0.7 is under review and passed QA
*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
*We are now 3 weeks from feature freeze for 5.2
*SPDX 3.0 has merged and is now the default.
*The project autobuilder has upgraded the controller to buildbot 4.2 which was tricky due to our custom plugin and changes to the framework used for the UI. The new UI should have the same functionality and seems faster and easier to use in places.
*We updated to glibc 2.40, thanks Khem. There is an issue with building pseudo under the new glibc version which is being worked on.
*We’d like to request help to process the open github pull requests for openembedded-core and bitbake:
*We identified an issue which meant warnings/errors in nativesdk recipes were not showing on our autobuilder. We have the fix for the CI issue ready as soon as we fix those warnings/errors, the gcc path problems are proving tricky.
**https://github.com/openembedded/openembedded-core/pulls
*We were able to optimize some space usage in builds, thanks Ross. The results are visible on our performance charts, e.g.: https://autobuilder.yocto.io/pub/non-release/20240723-5/testresults/buildperf-alma8/perf-alma8_master_20240723030045_28fd497a26.html https://autobuilder.yocto.io/pub/non-release/20240723-4/testresults/buildperf-debian11/perf-debian11_master_20240722200022_28fd497a26.html
**https://github.com/openembedded/bitbake/pulls
*Further help on optimizing build disk usage would be most welcome.
*Having these open doesn’t look good for the projects and we can’t disable them, some have been open for a long time. We did already clean up the poky pull requests.
*Some larger patches still need help with review these would be appreciated:
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
**Improved CVE tooling from Marta
*There are multiple occasional but annoying autobuilder failures we could do with help debugging/fixing, summarized by https://valkyrie.yocto.io/pub/non-release/abint/ :
**kernel fitimage changes from Adrian
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
**bitbake-setup and configuration fragments from Alexander
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
*We’ve been trying to resolve some of the longer standing patches in review and are getting more caught up.
***https://bugzilla.yoctoproject.org/show_bug.cgi?id=15463
**dnf failures in where ssh appears to fail, usually on qemumips but also seen on qemuarm: https://bugzilla.yoctoproject.org/show_bug.cgi?id=13674
**Ongoing CDN failures
**New memory allocation issues hinting we may need to scale builds back
*We are open to help developing patches to help debug issue further or other ideas on the causes and/or ways to mitigate them
*The Linux Foundation published information on navigating global regulations and sanctions: https://www.linuxfoundation.org/blog/navigating-global-regulations-and-open-source-us-ofac-sanctions
*Please contact TSC members if there are questions/concerns.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.
*Gold linker support was removed from core.
*Linux 6.6 was removed so we now just have the 6.12 kernel we plan to release YP 5.2 with.
*The performance metric charts were improved to be able to show both commit based and time based data, allowing performance changes to be isolated more easily.
*The triage team decided to clear out the “newcomer” bugs in bugzilla since the remaining ones were likely too hard without specialist knowledge. We’d love to see new/realist newcomer bugs being added.
*The 5.2 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, thanks to all who have contributed so far!


'''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.1. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.1_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.
Line 33: Line 47:


'''Tracking Metrics:'''<br/>
'''Tracking Metrics:'''<br/>
*WDD 2782 (last week 2787) (https://wiki.yoctoproject.org/charts/combo.html)
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
*OE-Core/Poky Patch Metrics
**Total patches found: 1079 (last week 1082)
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 178 (16%) [last week 178 (17%)]
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/pub/non-release/patchmetrics/
*https://autobuilder.yocto.io/-release/patchmetrics/


'''YP 5.1 Milestone Dates:'''<br/>
'''YP 5.2 Milestone Dates:'''<br/>
*YP 5.1 M2 is in QA.
*YP 5.2 M2 was released.
*YP 5.1 M3 Build date 2024-08-26
*YP 5.2 M3 Build Date 2025-03-03
*YP 5.1 M3 Release date 2024-09-06
*YP 5.2 M3 Release Date 2025-03-14
*YP 5.1 M4 Build date 2024-09-30
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.1 M4 Release date 2024-10-25
*YP 5.2 M4 Release Date 2025-04-25


'''Upcoming dot releases:'''<br/>
'''Upcoming dot releases:'''<br/>
*YP 4.0.20 is ready for release.
*YP 5.0.7 is in review.
*YP 5.0.3 Build Date 2024-08-12
*YP 4.0.25 Build Date 2025-02-17
*YP 5.0.3 Release Date 2024-08-23
*YP 4.0.25 Release Date 2025-02-28
*YP 4.0.21 Build Date 2024-09-09
*YP 5.1.3 Build Date 2025-02-24
*YP 4.0.21 Release Date 2024-09-20
*YP 5.1.3 Release Date 2025-03-07
*YP 5.0.4 Build Date 2024-09-23
*YP 5.0.8 Build Date 2025-03-10
*YP 5.0.4 Release Date 2024-10-04
*YP 5.0.8 Release Date 2025-03-21
*YP 4.0.22 Build Date 2024-10-14
*YP 5.1.4 Build Date 2025-03-24
*YP 4.0.22 Release Date 2024-10-25
*YP 5.1.4 Release Date 2025-04-04
*YP 5.0.5 Build Date 2024-11-11
*YP 4.0.26 Build Date 2025-04-07
*YP 5.0.5 Release Date 2024-11-22
*YP 4.0.26 Release Date 2025-04-18
*YP 4.0.23 Build Date 2024-11-18
*YP 5.0.9 Build Date 2025-04-21
*YP 4.0.23 Release Date 2024-11-29
*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:'''<br/>
'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
Line 65: Line 85:


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

Revision as of 15:53, 11 February 2025

Yocto Project Weekly Status Feb. 11th, 2025

Current Dev Position: YP 5.2 M3
Next Deadline: YP 5.2 M3 Build date 2025-03-03

Next Team Meetings:

Key Status/Updates:

Ways to contribute:

  • 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 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.
  • 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
  • We have a growing number of bugs in bugzilla, any help with them is appreciated.

Tracking Metrics:

YP 5.2 Milestone Dates:

  • YP 5.2 M2 was released.
  • YP 5.2 M3 Build Date 2025-03-03
  • YP 5.2 M3 Release Date 2025-03-14
  • YP 5.2 M4 Build Date 2025-03-31
  • YP 5.2 M4 Release Date 2025-04-25

Upcoming dot releases:

  • YP 5.0.7 is in review.
  • YP 4.0.25 Build Date 2025-02-17
  • YP 4.0.25 Release Date 2025-02-28
  • YP 5.1.3 Build Date 2025-02-24
  • YP 5.1.3 Release Date 2025-03-07
  • YP 5.0.8 Build Date 2025-03-10
  • YP 5.0.8 Release Date 2025-03-21
  • 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=86550"