Current Dev Position: YP 6.1 M2 Next Deadline: YP 6.1 M2: w/c 2026-07-20
Next Team Meetings: - Bug Triage meeting - Thursday 9th July 7:30am PDT ( https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) - Weekly Project Engineering Sync - Tuesday 7th July 8am PDT ( https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09) <https://zoom.us/j/990892712> - Yocto Project Patch Review - Thursday 9th July 10am GMT and Monday 13th July 9am PDT ( https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1) Project data dashboard: https://dashboard.yoctoproject.org/ Key Status/Updates: - YP 6.1 M1 was released - YP 6.0.2 is in review - YP 5.0.19 is in QA - We are now two weeks away from M2! - We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383 - We are having some challenges with the autobuilder, both with an NFS server open file/lock build up of some kind causing slowdown and eventual halting of write operations and also a mkdir cache race issue. We are working to debug both issues but it is distracting from other work like patch review and new development (e.g. layer.conf format changes). - Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359 - We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing. - We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled. - We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. - A key pseudo memory corruption issue when interacting with bash was identified and patches are being worked on for a new pseudo release to address this. - Intermittent build failures continue to be problematic: - several qemu ‘hang’ type issues - sometimes yocto-check-layer is showing checksum mismatch issues - siggen reset issues (“ResourceWarning: unclosed transport”) - groff build race issues - intermittent ptest failures in many recipes - We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto Want to contribute? We would appreciate help with the following areas: - We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=--- - There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/ - Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes. - For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing New to the project? - We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER Tracking Metrics: - WDD 2689 (last week 2647) ( https://wiki.yoctoproject.org/charts/combo.html) - OE-Core/Poky Patch Metrics - Total patches found: 1037 (last week 1036) - Patches in the Pending State: 145 (14%) [last week 145 (14%)] - https://valkyrie.yocto.io/pub/non-release/patchmetrics/ Upcoming development releases: - 6.1 M2: - Build Date: w/c 2026-07-20 - Release Date: w/c 2026-08-03 - 6.1 M3: - Build Date: w/c 2026-08-31 - Release Date: w/c 2026-09-14 - 6.1.0: - Build Date (M4): w/c 2026-10-12 - Release Date: w/c 2026-11-02 Upcoming dot releases: - YP 5.0.19 is in QA. - Release Date w/c 2026-07-13 - YP 6.0.3 - Build Date w/c 2026-08-10 - Release Date w/c 2026-08-24 - YP 5.0.20 - Build Date w/c 2026-08-17 - Release Date w/c 2026-08-31 - For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar 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 (#240401): https://lists.openembedded.org/g/openembedded-core/message/240401 Mute This Topic: https://lists.openembedded.org/mt/120157388/21656 Group Owner: [email protected] Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
