Current Dev Position: YP 5.2 M2 Next Deadline: YP 5.2 M2 Build date 2025-01-20
Next Team Meetings: - Bug Triage meeting Thursday Jan. 16th at 7:30 am PST ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) - Weekly Project Engineering Sync Tuesday Jan. 14th at 8 am PST ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09) <https://zoom.us/j/990892712> - Twitch - See https://www.twitch.tv/theyoctojester Key Status/Updates: - YP 5.2 M1 has two major QA issues, one for beaglebone and one for beagleplay A potential fix merged for the first issue, the second remains unresolved, kernel stable upgrades did not fix it. https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703 https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704 - YP 5.2 M2 is due to build next week and we haven’t resolved M1 yet! - YP 5.0.6 has been approved for release - YP 5.1.2 and 4.0.24 are queued in QA - There is some discussion about toolchain selection mechanisms via virtual/cross-cc providers on the architecture list which could help with clang integration. - There are discussions about how to implement “manifest” based fetchers to handle cargo, go and npm amongst others. We need to solve this problem in a way which everyone can work with but there is limited feedback or involvement in the patch review. Help is needed here to get this right and solve the long standing problems with these forms of software. Thanks to everyone already involved in the discussions. - We were able to upgrade rust to 1.81, thanks! - Various other key changes were merged (fragment handling fix, aclocal cleanup, qemu options fixes, flag ??= support, pytest improvements, deb multilib fixes and more) - A native class extension fix merged but it may cause some wider metadata issues short term since new dependencies are being exposed. - 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: - 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 <https://autobuilder.yocto.io/pub/non-release/patchmetrics/> - We have a growing number of bugs in bugzilla, any help with them is appreciated. - Regarding bugs, even if you can’t fix a bug, submitting a failing test case that can reproduce the issue significantly improves the chances it might get fixed. - Further help on optimizing build disk usage would be most welcome. Tracking Metrics: - WDD 2763 (last week 2840) ( https://wiki.yoctoproject.org/charts/combo.html) - OE-Core/Poky Patch Metrics - Total patches found: 1030 (last week 1037) - Patches in the Pending State: 174 (17%) [last week 174 (17%)] - https://autobuilder.yocto.io/pub/non-release/patchmetrics/ YP 5.2 Milestone Dates: - YP 5.2 M1 in review. - YP 5.2 M2 Build Date 2025-01-20 - YP 5.2 M2 Release Date 2025-01-31 - 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.6 is ready for release. - YP 4.0.24 in QA. - YP 5.1.2 in QA. - YP 5.0.7 Build Date 2025-01-27 - YP 5.0.7 Release Date 2025-02-07 - 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 The Status reports are now stored on the wiki at: https://wiki.yoctoproject.org/wiki/Weekly_Status [If anyone has suggestions for other information you’d like to see on this weekly status update, let us know!] Thanks, *Stephen K. Jolley* *Yocto Project Program Manager* ( *Cell*: (208) 244-4460 * *Email*: *s <[email protected]>[email protected] <[email protected]>*
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#64549): https://lists.yoctoproject.org/g/yocto/message/64549 Mute This Topic: https://lists.yoctoproject.org/mt/110609642/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/yocto/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
