Yocto Project - User contributions [en]

2026 Yocto Project Weekly Status Archive

2026-04-14T14:47:32Z

Stephen K. Jolley: /* Yocto Project Status 7 April 2026 */

== Yocto Project Status 14 April 2026 ==
Current Dev Position: YP 6.0 M4 
Next Deadline: YP 6.0 M4 Build Date 2026-04-20 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 16th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 14th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 16th 10am GMT and Monday Apr. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.17 is due to be released
*YP 6.0 M3 is in QA
*YP 4.0.35 is queued for QA
*We have converted over to sbom-cve-check and dropped cve-check. This has caused a significant increase in CVEs reported, these are being triaged.
*Issues with pending work needed:
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Reports of pseudo errors on Fedora 44 beta related to openat2()
**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
**Meta-oe cve layer filtering under new tooling (metrics script tweak?)
**Reprodicubility issues with strace/apr-util after gnulib macro changes (patches in testing)
*There was disruption to git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.
git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The final kirkstone build has taken place and we’re no longer planning to merge patches on this branch.
*If you have any final patches for whinlatter, please get these sent to the list ASAP.

'''Ways to contribute:''' 
*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 2777 (last week 2797) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1072 (last week 1060)
**Patches in the Pending State: 147 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 in QA.
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.17 is in review.
*YP 4.0.35 is in QA.
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*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 
== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues with pending work needed:
**Converting scripts/run-cvecheck to sbom-cve-check
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds (need tags)
**Ubuntu 26.04 support (need worker adding for testing)
*Issues that have patches ready to merge:
**DISTRO_FEATURES defaults improvements.
**Fixing yocto-check-layer to work with --machines
**RHEL 9 xattrs/selinux/tar issue
**Splitting wic into an external tool.
**RHEL 10/openSUSE Leap 16.0 support
*Issues that need investigation
**Reports of pseudo errors on Fedora 44 beta
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*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 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA.
*YP 4.0.35
**Build Date 2026-04-06
**Release Date 2026-04-22
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*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 

== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.34 was released.
*YP 5.3.3 is approved for release.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues still pending:
**Splitting wic into an external tool.
**Converting scripts/run-cvecheck to sbom-cve-check
**DISTRO_FEATURES defaults improvements.
**RHEL 9 xattrs/selinux/tar issue
**How to improve DEBUG_BUILD?
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*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 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 was released.
*YP 5.3.3 ready for release.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 M2 has been released.
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-04-14T14:47:00Z

Stephen K. Jolley: /* Yocto Project Status 7 April 2026 */

2026 Yocto Project Weekly Status Archive

2026-04-07T14:44:31Z

Stephen K. Jolley: /* Yocto Project Status 31 March 2026 */

== Yocto Project Status 7 April 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 9th 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 7th 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 9th 10am GMT and Monday Apr. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues with pending work needed:
**Converting scripts/run-cvecheck to sbom-cve-check
**32bit x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds (need tags)
**Ubuntu 26.04 support (need worker adding for testing)
*Issues that have patches ready to merge:
**DISTRO_FEATURES defaults improvements.
**Fixing yocto-check-layer to work with --machines
**RHEL 9 xattrs/selinux/tar issue
**Splitting wic into an external tool.
**RHEL 10/openSUSE Leap 16.0 support
*Issues that need investigation
**Reports of pseudo errors on Fedora 44 beta
*The proposed wic changes will need wic support files to be placed in files/wic within layers going forwards.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*We are aware of our git hosting giving 502 Bad Gateway errors, this is being investigated
*The CFP for the Yocto Project Workshop at Embedded Recipes 2026 closes today: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*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 2797 (last week 2814) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1062)
**Patches in the Pending State: 148 (14%) [last week 148 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.3 was released.
*YP 5.0.17 is in QA.
*YP 4.0.35
**Build Date 2026-04-06
**Release Date 2026-04-22
*YP 5.3.4
**Build Date 2026-04-20
**Release Date 2026-05-06
*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 
== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.34 was released.
*YP 5.3.3 is approved for release.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues still pending:
**Splitting wic into an external tool.
**Converting scripts/run-cvecheck to sbom-cve-check
**DISTRO_FEATURES defaults improvements.
**RHEL 9 xattrs/selinux/tar issue
**How to improve DEBUG_BUILD?
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*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 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 was released.
*YP 5.3.3 ready for release.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 M2 has been released.
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-04-07T14:44:14Z

Stephen K. Jolley: /* Yocto Project Status 31 March 2026 */

2026 Yocto Project Weekly Status Archive

2026-03-31T14:49:07Z

Stephen K. Jolley: /* Yocto Project Status 24 March 2026 */

== Yocto Project Status 31 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 2nd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 31st Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 2nd 10am GMT and Monday Apr. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.34 was released.
*YP 5.3.3 is approved for release.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are still key changes missing.
*Issues still pending:
**Splitting wic into an external tool.
**Converting scripts/run-cvecheck to sbom-cve-check
**DISTRO_FEATURES defaults improvements.
**RHEL 9 xattrs/selinux/tar issue
**How to improve DEBUG_BUILD?
**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Fixing yocto-check-layer to work with --machines (many fixes merged)
*Issues that were resolved this week:
**Sbom-cve-check added
**Replacement of runtlp with kirk (Thanks Daniel!)
**bitbake-setup vscode integration
**Fedora 43 selftest failures
**Reconciling poky and OE-Core defaults templates.
*We have rationalized the tags in various project repositories, more information can be found here: https://lists.openembedded.org/g/openembedded-architecture/message/2312 Whilst controversial, this will make the tag list much easier to understand for users, guide users to use the right tags going forward and remove confusion about whether any tags were “missed”, at the expense that some CI setups may need adjusting short term.
*We’re working through the backlog of patches and intermittent build failures are still problematic, including the emergence of new issues (newer kernel version?). We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The CFP closing date for the Yocto Project Workshop at Embedded Recipes 2026 has been extended until April 7th, please submit a proposal if you’d like to present: https://pretalx.com/yocto-embedded-recipes-2026/cfp

'''Ways to contribute:''' 
*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 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1062 (last week 1072)
**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 was released.
*YP 5.3.3 ready for release.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 M2 has been released.
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-03-31T14:48:32Z

Stephen K. Jolley: /* Yocto Project Status 24 March 2026 */

2026 Yocto Project Weekly Status Archive

2026-03-24T14:43:35Z

Stephen K. Jolley: /* Yocto Project Status 17 March 2026 */

== Yocto Project Status 24 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Mar. 10am GMT and Monday 30th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 6.0 M2 has been released.
*YP 4.0.34 is due to be released.
*YP 5.3.3 is in review after QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
**Issues still pending:
**Splitting wic into an external tool.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*Issues that are mostly known quantities still needing work:
**x86 kvm seemingly broken with certain CPU features (#16074)
**Failure to generate regression reports in release builds
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
**Fixing yocto-check-layer to work with –machines
*Issues that were resolved this week:
**Switching to pkg-config.
**Allowing non-destructive git fetcher updates for bitbake-setup (further tweaks still being discussed)
*We are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due to xattrs)
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 was released.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 4.0.34 ready for release.
*YP 5.3.3 is in review.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-03-24T14:43:05Z

Stephen K. Jolley: /* Yocto Project Status 17 March 2026 */

2026 Yocto Project Weekly Status Archive

2026-03-17T14:52:08Z

Stephen K. Jolley: /* Yocto Project Status 10 March 2026 */

== Yocto Project Status 17 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Mar. 10am GMT and Monday 23rd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.2 has been released
*YP 6.0 M2 is due to be released
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
*We have issues we need to resolve before M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Resolve Fedora 43 selftest failures
*glibc was upgraded 2.43 and we released a new uninative to match
*runqemu now has better handling for different display outputs including VNC on unix domain sockets
*We are adding testing of ptests on musl to our test matrix
*Kernel rust support has merged
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

'''Ways to contribute:''' 
*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 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1069 (last week 1081)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is ready for release.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 is in QA.
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-03-17T14:51:44Z

Stephen K. Jolley: /* Yocto Project Status 10 March 2026 */

2026 Yocto Project Weekly Status Archive

2026-03-10T14:56:48Z

Stephen K. Jolley: /* Yocto Project Status 3 March 2026 */

== Yocto Project Status 10 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-23 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10th Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Mar. 10am GMT and Monday 16th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.16 has been released
*YP 5.3.2 is due to be released
*YP 6.0 M2 is in QA
*YP 4.0.34 is in QA.
*YP 6.0 M3 is the feature freeze for 6.0 which is our next LTS.
*YP 6.0 M3 is due to build in 2 weeks however there are many key changes needed still missing.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before M3:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
**Switch to internal VNC server in QEMU
**update to glibc 2.43 so we can release a new uninative
*We identified a number of timeout/buffer related issues in and around ptest-runner and whilst we’re still in early stages of testing, these look to significantly improve autobuilder intermittent ptest failures, particularly on qemuriscv64.
*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*On scarthgap, we have updated to openssl 3.5 since that is still maintained
*The project has a booth at Embedded World this week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1081 (last week 1103)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-23
*YP 6.0 M3 Release Date 2026-04-08
*YP 6.0 M4 Build Date 2026-04-13
*YP 6.0 M4 Release Date 2026-05-04

'''Upcoming dot releases:''' 
*YP 5.0.16 is released.
*YP 5.3.2 is released.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-16
*YP 5.3.3 Release Date 2026-04-01
*YP 5.0.17 Build Date 2026-03-30
*YP 5.0.17 Release Date 2026-04-15
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-22
*YP 5.3.4 Build Date 2026-04-20
*YP 5.3.4 Release Date 2026-05-06
*YP 5.0.18 Build Date 2026-04-27
*YP 5.0.18 Release Date 2026-05-13
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-03-10T14:56:17Z

Stephen K. Jolley: /* Yocto Project Status 3 March 2026 */

2026 Yocto Project Weekly Status Archive

2026-03-03T15:56:30Z

Stephen K. Jolley: /* Yocto Project Status 24 February 2026 */

== Yocto Project Status 3 March 2026 ==
Current Dev Position: YP 6.0 M3 
Next Deadline: YP 6.0 M3 Build Date 2026-03-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Mar. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashbard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 has been released
*YP 5.0.16 is in TSC review
*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
**We are aware of changes in QA timelines and are discussing how to address them.
*We have issues which need further work that will block M3:
**x86 kvm seemingly broken with certain CPU features (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
**Failure to generate regression reports in release builds
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup.
**Splitting wic into an external tool.
**Kernel rust support.
**Switching to pkg-config.
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES defaults improvements.
**SBOM/cve-check changes.
**Reconcile poky and OE-Core defaults templates.
*OE-Core switched to enabling a hash equivalence server by default.
*We’re working through the backlog of patches and the high number of intermittent build failures is still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!

'''Ways to contribute:''' 
*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 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 11063 (last week 1107)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 is in QA.
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 is in review.
*YP 5.3.2 is in QA.
*YP 4.0.34 is in QA.
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Status 24 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 26th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 24th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 26th Feb. 10am GMT and Monday 2nd Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is due for release
*YP 5.0.16 is in QA
*YP 5.2.3 is queued for QA
*YP 6.0 M2 is due to build when we have patches merged
*We have two open high issues which need further work that will block M3:
**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
*We also have issues we need to resolve before release:
**Allowing non-destructive git fetcher updates for bitbake-setup
**Splitting wic into an external tool
**Kernel rust support
**Switching to pkg-config
**Deprecation of ltp (upstream dropped runltp and mandate kirk)
**How to improve DEBUG_BUILD?
**DISTRO_FEATURES changes to ‘nodistro’ in OE-Core
**SBOM/cve-check changes
*We updated “nodistro” to use 3 of the include files poky was already using:
**Space optimization to reduce build footprint and sstate object size
**Disabling most static libraries by default (build size/speed wins)
**Enabling security flags by default
*“nodistro” now also enables uninative by default to allow for better CDN sstate reuse
*Distros now need to use INIT_MANAGER to select their preferred init system with the default being systemd for “nodistro”. Poky’s defaults remain unchanged and we don’t have plans to change this at this time due to the work involved and impact (e.g test result comparisons).
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1107 (last week 1108)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 17 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 19th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 17th Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 19th Feb. 10am GMT and Monday 23rd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.33 is awaiting approval
*YP 5.0.16 is in QA
*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
**AB-INT: do_image_wic: tar command return exit status 2 (#16143)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them
*We removed sysvinit compatibility support from systemd images since this will not be supported by upstream during the lifespan of our upcoming LTS release.
*We removed legacy tls support from openssl in the interests of providing better secure defaults.
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1108 (last week 1106)
**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 10 February 2026 ==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 12th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 10rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 12th Feb. 10am GMT and Monday 16th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 was released
*YP 6.0 M1 was released
*YP 4.0.33 is in QA
*YP 6.0 M2 is due to build next week.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved:
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**rust do_test_compile/do_install segfault (#16058)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: opkg-build segmentation fault (#16078)
*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic - we continue to prioritise addressing these since any given build is now statistically likely to hit one or more of them.
*Patch review is now using two branches:
**“master-review” - patches which pass on the autobuilder and will be discussed on the patch review call (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-review)
**“master-backlog” - patches which have been discussed and need further investigation or more detailed feedback which we haven’t had time for yet (https://git.openembedded.org/openembedded-core-contrib/log/?h=master-backlog)
*Patches are merging but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1106 (last week 1100)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.33 is in QA.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-03-03T15:55:46Z

Stephen K. Jolley: /* Yocto Project Status 24 February 2026 */

Weekly Status

2026-02-09T21:34:11Z

Stephen K. Jolley: /* Yocto Project Status 3 February 2026 (WW06) */

2026 Yocto Project Weekly Status Archive

2026-02-09T21:33:47Z

Stephen K. Jolley: /* Yocto Project Status 3 February 2026 (WW06) */

== Yocto Project Status 3 February 2026==
Current Dev Position: YP 6.0 M2 
Next Deadline: YP 6.0 M2 Build Date 2026-02-16 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 5th Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 3rd Feb. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 5th Feb. 10am GMT and Monday 9th Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3.1 is due to be released
*YP 6.0 M1 is in QA
*YP 4.0.33 is queued for QA after 6.0 M1
*YP 6.0 M2 is now targeting a build date of 16th Feb. This will give us three weeks each for M3 (target date 9th March) and M4 (target build date 30th March).
*Good progress has been made with the autobuilder issues but we still don’t have the stability in builds we need for reliable project operations.
*There are currently 5 high open bugs, which will block M2. Three have line of sight to being resolved (Thanks Alex and Michael!):
**Issues reusing binaries from fedora 42/43 on older systems (#16087)
**Hangs of the autobuilder controller (database locking?) (#16129)
**Generation of releases.json needs updating (#16138)
*Two are currently needing further work:
**rust do_test_compile/do_install segfault (#16058)
**x86 kvm broken on Fedora 43 (#16074)
*“build-sysroots: useradd command did not succeed” (#16135) was fixed, thanks Adrian!
*The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2945 (last week 2978) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1100 (last week 1097)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-16
*YP 6.0 M2 Release Date 2026-02-27
*YP 6.0 M3 Build Date 2026-03-09
*YP 6.0 M3 Release Date 2026-03-20
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 27th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M2 Build Date 2026-02-02 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 29th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 27th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 29th Jan. 10am GMT and Monday 2nd Feb. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
* YP 5.0.15 was released
* YP 5.3.1 is under review
* YP 6.0 M1 is in QA
* YP 4.0.33 is queued for QA after 6.0 M1
* YP 6.0 M2 is due next week!
* Good progress has been made with the autobuilder issues and an M1 build is in QA but we still don’t have the stability in builds we need for reliable project operations.
* There are currently 6 high open bugs, which will block M2:
** Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
** x86 kvm broken on Fedora 43 (#16074)
** AB-INT: build-sysroots: useradd command did not succeed (#16135)
** Hangs of the autobuilder controller (database locking?) (#16129)
** Generation of releases.json needs updating (#16138)
* The number of intermittent failures affecting builds, both stable and development, continues to be problematic. Any given build is now statistically likely to hit one or more of them and we often don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
* Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.

'''Ways to contribute:''' 
*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 2978 (last week 3041) (https://wiki.yoctoproject.org/charts/combo.html)
* OE-Core/Poky Patch Metrics
** Total patches found: 1097 (last week 1099)
** Patches in the Pending State: 152 (14%) [last week 152 (14%)]
* https://valkyrie.yocto.io/pub/non-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.3.1 is under review.
*YP 4.0.33 is queued for QA after 6.0 M1.
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-01-20T16:06:34Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 20th, 2026 */

2026 Yocto Project Weekly Status Archive

2026-01-20T16:06:12Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 13th, 2026 */

== Yocto Project Weekly Status Jan. 20th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 22nd Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 20th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 22nd Jan. 10am GMT and Monday 26th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when we have resolved enough issues to mean the build is likely to succeed and the release of sufficient quality
*Good progress has been made with the autobuilder issues and builds now complete but contain failures.
*There are currently 6 high open bugs, some of which block M1, some could be deferred to M2:
**Hangs of the autobuilder controller (database locking?) (#16129)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
**x86 kvm broken on Fedora 43 (#16074)
**AB-INT: build-sysroots: useradd command did not succeed (#16135)
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We are holding some dedicated meetings to triage these and find ways of removing the failures from our builds which may include reducing testing.
*Patches are merging again but there is a backlog and we’ve had to prioritize simpler changes. We continue to struggle for bandwidth for changes needing in depth review/feedback.

'''Ways to contribute:''' 
*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 3041 (last week 3026) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1089)
**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-01-20T16:05:33Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 13th, 2026 */

2026 Yocto Project Weekly Status Archive

2026-01-13T15:53:43Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 6th, 2026 */

== Yocto Project Weekly Status Jan. 13th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 15th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 13th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 15th Jan. 10am GMT and Monday 19th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*There are also 4 high bugs open for 6.0 M2.
*We are seeing multiple serious issues blocking 6.0 M1 from building:
**A glibc test causing builds to hang (a buffer overflow SIGABRT in unfs3 triggered by host compiler + fortify source) (#16113)
**Hangs of the autobuilder controller (database locking, should be fixed) (#16129)
**Issues with a CVE patch applied to tar in rocky9/alma9/centos-stream using the openat2 syscall which pseudo doesn’t wrap (#16117)
**Issues reusing binaries from fedora 43 (and maybe ubuntu 25.10) on older systems (patchelf triggered?) (#16074, #16087)
**still need to disable the npm fetcher (#16105)
*We have not had this number of high bugs blocking releases in several years
*The number of intermittent failures affecting stable release builds is becoming problematic. Any given build is now statistically likely to hit one or more of them and we don’t have successful builds. Since we struggle to get help in addressing these, we need to change and start potentially blocking releases (including stable/LTS) until these get addressed in some way. We plan to form a dedicated team to investigate these and find ways of removing the failures from our builds which may include reducing testing.
*To be clear, due to the problems above, most patch testing is now stalled as the autobuilder is currently inoperable and we can’t test anything.
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!

'''Ways to contribute:''' 
*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 3026 (last week 3011) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1092)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 is under review.
*YP 5.3.1 in QA.
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-01-13T15:53:03Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 13th, 2026 */

Weekly Status

2026-01-13T15:45:42Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 13th, 2026 */

2026 Yocto Project Weekly Status Archive

2026-01-13T15:39:16Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 6th, 202 */

== Yocto Project Weekly Status Jan. 6th, 2026 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-01-13T15:38:55Z

Stephen K. Jolley: /* Yocto Project Weekly Status Jan. 6th, 202 */

2026 Yocto Project Weekly Status Archive

2026-01-06T15:43:43Z

Stephen K. Jolley: Created page with "== Yocto Project Weekly Status Jan. 6th, 202 == Current Dev Position: YP 6.0 M1 Next Deadline: YP 6.0 M1 Build Date 2026-01-05 6 '''Next Team Meetings:''' *Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09) *Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09) *Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Mon..."

== Yocto Project Weekly Status Jan. 6th, 202 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 
6
'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan. 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan. 10am GMT and Monday 12th Jan. 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.15 is in QA
*YP 6.0 M1 will build when the 5 open high bugs are resolved.
*We have a number of issues with build performance tests, test results and hanging glibc NFS tests on the autobuilder which need to be resolved before we can build a new release.
*Due to the number of problems currently present, patch merging will have to slow to avoid adding any further issues.
*Yoann Congal is starting to ramp up as the new LTS maintainer to take over from Steve Sakoman
*The linux kernel is now defaulting to 6.18 and the other versions will soon be removed.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105)..

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3011 (last week 2991) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1092 (last week 1090)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.15 in QA.
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC

Weekly Status

2026-01-06T15:43:02Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 23th, 2025 */

Weekly Status

2026-01-06T15:39:08Z

Stephen K. Jolley:

Weekly Status

2025-12-23T15:55:37Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 16th, 2025 */

2025 Yocto Project Weekly Status Archive

2025-12-23T15:55:20Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 23th, 2025 */

== Yocto Project Weekly Status Dec. 23th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan 10am GMT and Monday 5th Jan 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.32 has now been released!
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*Linux kernel 6.18 recipes are now available for testing but aren’t the default yet. Issues in OE-core are mostly resolved with some issues remaining for other layers. Wider testing is welcome as this will be the LTS kernel.
*Linux-libc-headers was also updated to 6.18, the 6.17 recipes were removed and 6.16 and 6.12 saw point release upgrades.
*Support for symlinking existing local repos with bitbake-setup has merged. There is ongoing work to simplify using a common hashequiv instance and sstate.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105).

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 2981) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1090 (last week 1083)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 was released.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 4.0.32 is in QA
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 is released.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 is in QA.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 4.0.32 is in QA
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 is released.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 is in QA.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 was released
*YP 5.3 rc4 has passed QA and is under review
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in review for release.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 was released.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is due to be released
*YP 5.3 rc4 is built and due to enter QA
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in QA.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 25th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 27th 10am GMT and Monday Dec. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is under review for release.
*The final 5.3 build is still pending on fixing bugs from issues arising from the bitbake-setup changes. All other changes are now on hold for post release.
*We aim to build 5.3 when we have stable builds on the autobulder. Fixes from the changes around MACHINE/DISTRO conflict between conf/env and feature settings broke oe-selftest. The cooker feature change also exposed two existing bitbake *cache issues, particularly with memory resident bitbake. Those fixes merged but the fixes appear to be exposing further problems which are being investigated.
*Other potential changes that have been discussed but don’t have workable patches yet and are not going to block release::
**to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2953 (last week 2943) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1066)
**Patches in the Pending State: 152 (14%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 18th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 20th 10am GMT and Monday Nov. 24th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*The final 5.3 build is still pending on resolving some rough edges on bitbake-setup. The patches so far have made a huge difference, thanks everyone who helped!
*We aim to build 5.3 when the remaining identified issues with bitbake-setup are resolved:
**Improvements to the default build directory path (json format string?)
**Handling potential MACHINE/DISTRO conflict between conf/env and feature settings
**Comments to toolcfg.conf about how to change
**Mention "bitbake-config-build enable-fragment machine/XXX" in bitbake-setup output
**Remove/change broken template files from meta-yocto
*Other potential changes that have been discussed but don’t have workable patches yet:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2943 (last week 3048) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1066 (last week 1067)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 11th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 13th 10am GMT and Monday Nov. 17th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 was released
*YP 4.0.31 is due to be released
*We are not yet ready to build 5.3 as there are too many rough edges on bitbake-setup: https://lists.openembedded.org/g/openembedded-architecture/message/2199
*The documentation changes related to bitbake-setup merged, thanks to all who have helped on these.
*We are now no longer updating the poky master branch. The distro in meta-yocto remains. Long live poky.
*Toaster is now working with bitbake-setup, huge thanks to David Reyna for resolving the issues there.
*Upstream linux kernel end-of-life’d 6.16 but we can’t get 6.17 working fully so we’ll be releasing with 6.16 and removing the 6.17 recipes (merged in error).
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.
*We removed tcp-wrappers from OE-Core. It was late in but this should have happened long ago and if anyone is using it, you probably shouldn’t be!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3048 (last week 3103) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1098)
**Patches in the Pending State: 175 (16%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 was released.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 4.0.31 is in review for release.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 was released
*YP 5.3 M3 is due to be released
*YP 4.0.31 is in QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in review for release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 was released.
*YP 4.0.31 is in QA.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 is in QA
*YP 5.0.13 is under review for release
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 is in review for release.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 21st, 2025 ==
Current Dev Position: YP 5.3 M4 
Next Deadline: YP 5.3 M4 Build Date 2025-10-06 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday Oct. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 and 5.0.13 currently in QA.
*YP 5.2.4 has been released
*We’re at feature freeze for YP 5.3. Patches that will be accepted now have a higher bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve this issues!
*Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has been deleted. Many thanks to Deepesh and others at Wind River!. There’s a known regression building rust with clang which is being investigated.
*Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with 6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have to see as to whether we upgrade post-release.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3009 (last week 2904) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1096)
**Patches in the Pending State: 153 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 was released.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 14th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 16th 10am GMT and Monday Oct. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 is in QA.
*YP 5.2.4 is due to be released.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. The status is:
**llvm/clang split patches have merged
**bitbake-setup has merged
**the autobuilder has switched to use bitbake-setup for master builds
**there are build issues with bitbake-setup that have shown up with check-layer targets
**fixes for the reproducibility problem in perf from 6.16 are being tested
*“poky” as a combo-layer repository will soon no longer be needed or updated.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2904 (last week 2884) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 is ready for release.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 7th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is under review.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (patches ready and in testing)
**Merging of bitbake-setup
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is ready for release.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 30th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 2nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 30th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 2nd 10am GMT and Monday Oct. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is under review for release
*YP 5.2.4 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (currently blocked by uninative issues with llvm static libs)
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2854 (last week 2846) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1105)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is ready for release.
*YP 5.2.4 is in QA.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 23rd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 25th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 23rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 25th 10am GMT and Monday Sept. 29th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still aim to merge before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2846 (last week 2828) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1105 (last week 1112)
**Patches in the Pending State: 154 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is in QA.
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 16th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 18th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 16th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 18th 10am GMT and Monday Sept. 22nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*We have now updated to the 6.16 linux kernel
*There are clang/llvm performance improvements we plan to merge before building 5.3 (Thanks Ross!)
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2828 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1112 (last week 1111)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 is due to be released.
*YP 5.0.12 is due to be released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*We aim to merge bitbake-setup before building 5.3 M3
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is being reviewed for release.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 2nd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 4th 10am GMT and Monday Sept. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*RP is on holiday this week so should not be working
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA
*YP 5.3 M3 is due to build shortly (and is feature freeze)
*Linux 6.16 has been integrated but is currently not the default
*Patches continue to merge into master for upgrades and fixes until M3 is built
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*The Embedded Linux Conference was a success, with lots of Yocto-related talks being full to capacity. The OpenEmbedded and Yocto Project mini conferences were well attended and very interesting. Thanks to everyone who attended and made it a great event!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2845 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1096)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 26th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 28th 10am GMT and Monday Sept. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 was released
*YP 5.2.3 is in QA
*YP 5.0.12 is waiting for QA
*YP 5.3 M3 is due to build in one week (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays and conferences.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A 6.16 kernel recipe is available but we haven’t switched to it yet
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2878) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 was released.
*YP 5.2.3 is in QA.
*YP 5.0.12 is waiting for QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 19th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 19th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 21st 10am GMT and Monday Aug. 25th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 is due to be released
*YP 5.2.3 is in QA
*YP 5.3 M3 is due to build in two weeks (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Lttng component upgrades merged (babeltrace2 python enabling, lttng-modules, lttng-ust and lttng-tools) after several issues were resolved, particularly ptest failures.
*The kernel upgrade to 6.16 is under development. The libc-headers merged and is no longer blocked on lttng due to the upgrades above.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*For M3, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2848 (last week 2838) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is ready release.
*YP 5.2.3 is in QA.
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 12th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 14th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 12th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 14th 10am GMT and Monday Aug. 18th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 was released
*YP 4.0.29 is in QA
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*Images are now .zst compressed by default
*Bitbake variable “filter” support merged, which is useful to make class extension internals (and hence parse time) more efficient.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Glibc was upgraded to 2.42 with a new uninative added for the new version
*The kernel upgrade to 6.16 is blocked on lttng-modules which doesn’t support the new kernel version yet.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2838 (last week 2841) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 was released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is in QA.
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 5th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 7th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 5th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 7th 10am GMT and Monday Aug. 11th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*xz is now a required host tool
*Patches are proposed to change the default images to be .zst compressed since these work better for releases and sharing
*Compressed images have implications for runqemu which needs to be run in snapshot mode to boot them
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2841 (last week 2826) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is to be released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 29th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 31st 10am GMT and Monday Aug. 4th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 rc2 is in QA
*YP 5.0.11 was released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The lldb reproducibility regression was resolved, thanks!
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress but nuch work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2826 (last week 2799) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is in QA.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.11 was released.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 22nd, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 24th 10am GMT and Monday July 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build this week.
*YP 5.2.2 was released
*YP 5.0.11 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*We have a reproducibility regression in lldb which needs fixing urgently due to CI failures.
*We were able to root cause and resolve the 5.3 M1 QA reported gtk-play regression.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X merged, thanks to everyone who helped with fixes.
*Fixes for bitbake for python 3.14 around multiprocessing have been proposed. There are also bitbake profiling fixes for python 3.12+ and some small performance tweaks.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2799 (last week 2824) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1099)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.2 was released.
*YP 5.0.11 is ready for release.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 15th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 17th 10am GMT and Monday July 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build next week however we still need to look into and fix the issue found in M1: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*Help in debugging and fixing this would be very welcome.
*YP 5.2.2 is due to be released.
*YP 5.0.11 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. Patches from Ross start to split up the clang build and helped with a 5% speed improvement, thanks!
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X is ready to merge for core. The fixes to meta-openembedded are much appreciated.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2824 (last week 2800) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 was released.
*YP 5.2.2 is ready for release.
*YP 5.0.11 is in QA.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 8th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 10th 10am GMT and Monday July 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 was released. We still need to look into and fix the issue found: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is due to be released.
*YP 5.2.2 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*There are problems with building native recipes with clang on the autobuilder which are suggesting deeper issues in our gcc files layout.
*A fix for a rare parsing hang has merged and some tweaks to the parsing queueing process are under discussion.
*cmake 4.X is ready to merge for code but is causing significant (~100 recipes) breakage in meta-openembedded. We will hold off a short while but this will merge soon. Khem needs help to fix the recipes there.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 3)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2800 (last week 2770) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 was released.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is ready for release.
*YP 5.2.2 is in QA.
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is in QA.
*Patches continue to merge into master for upgrades and fixes.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*The clang build time and size increases continue to cause significant concern.
*Patches to improve gomod support in devtool merged.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 is ready for release.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 24th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
*To support this, the layer series was updated to whinlatter in core.
*The clang build time and size increases continue to cause significant concern.
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
*OE-Core is adopting the use of glvnd for libGL abstraction
*The initial RISC-V tune changes merged
*Support for distro/machine selection with builtin fragments was added.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 in QSA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 17th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 19th 10am GMT and Monday June 23rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.10 was released
*YP 5.3 M1 is due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection patches have merged
*For M2, the following changes have been mentioned as possibilities:
**Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
**bitbake-setup
**bitbake config fragment support for distro/machine
**wic split from OE-Core
**RISC-V tune changes
**go/gomod fetcher changes

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2777 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1084 (last week 1089)
**Patches in the Pending State: 158 (15%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.10 was released.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 10th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June 16th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 were released.
*YP 5.0.10 is due to be released.
*YP 5.3 M1 is now due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*Patches were sent out for a proposed toolchain selection mechanism implementation, feedback/review is welcome.
*Icecc.bbclass was removed.
*lz4 was removed from HOSTTOOLS as it was unneeded.
*Fitimage restructuring was merged, thanks Adrian.
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder so far, huge thanks to Michael Halstead for working on this.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2740 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1089)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 was released.
*YP 5.2.1 was released.
*YP 5.0.10 is ready for release.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 3rd, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 5th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 3rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 5th 10am GMT and Monday June 9th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 are due to be released.
*YP 5.0.10 is in QA.
*YP 5.3 M1 is one weeks away
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection mechanism is proving challenging as both the toolchain inherit and class extensions like native both need to happen ‘last’ and both involve overrides that are involved in deferred inherits. This issue may need bitbake changes to resolve.
*Should we drop icecc.bbclass and let someone step up and maintain it in its own layer?
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2803) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1088)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is out for review.
*YP 5.0.10 is in QA.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 27th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 29th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 27th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 29th 10am GMT and Monday June 2nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in under review for release
*YP 5.2.1 is in QA
*YP 5.3 M1 is two weeks away
*Patches continue to merge into master for upgrades and fixes.
*Further pieces of the clang changes have merged.
*There is a potential pending change to wic to rename plugins, changing “-” to “_”, feedback welcome on if/how we should handle this as it could be invasive in impact.
*The clang build time and size increases continue to cause significant concern.
*fitimage changes from Adrian are nearly ready to merge once two issues have been resolved.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2803 (last week 2813) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1088 (last week 1096)
**Patches in the Pending State: 157 (14%) [last week 158 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is in QA.
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 20th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in QA
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*musl-qemuarm64 was also added to default testing
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*Many good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is in QA.
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 13th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 15th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 13th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 15th 10am GMT and Monday May 19th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 was released
*We’re happy to announce that RISC-V is becoming a officially supported architecture for Yocto Project: https://riscv.org/riscv-news/2025/05/risc-v-international-and-the-rise-project-join-forces-for-yocto-project-support/
**Thanks to all who helped make this happen!
*Patches merged to switch pseudo from a directory exclusion list to a directory inclusion list. This change has long been requested but is now working and merged.
*The clang merge caused significant build time increases (nearly double) as well as image size increases, all of which we need analysis to try and mitigate if possible.
*Qemu changes upstream mean running it on 32 bit hosts may soon not be possible. 64 bit emulation on 32 bit hosts has already been dropped.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Many other good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2791 (last week 2753) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1104 (last week 1075)
**Patches in the Pending State: 159 (14%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 was released.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 6th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 8th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 6th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 8th 10am GMT and Monday May 12th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 was released
*YP 5.2 rc2 is pending release and the rc1 issues were fixed
*The gcc 15 upgrade merged
*We merged the clang recipe into oe-core replacing llvm. There are further tweaks and improvements pending but this gives us a baseline to improve upon.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. Layers including meta-openembedded will need updating to avoid these accesses.
*Many other good upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2753 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1075 (last week 1071)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in review for release.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 was released.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 29th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 1st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 1st 10am GMT and Monday May 5th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 is pending release.
*YP 5.2 rc2 is in QA.
*We have fixes/workarounds merged for the most frequent recent autobuilder issues apart from the clang problem after the mesa merge and CDN issue (which is being worked on).
*Patches continue to merge into master as review/time/testing allows. We are seeing a high number of failures in incoming patches which take time to resolve.
*The gcc 15 upgrade is close to ready to merge but there are failures in layers outside core.
*The clang/llvm recipe merge patch series is now mostly passing autobuilder testing and would step us closer to the meta-clang merge. Review help appreciated.
*Various other upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2746) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1071 (last week 1068)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 rc2 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 is ready for release.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 22rd, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 22rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 24th 10am GMT and Monday Apr. 28th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*We plan to build YP 5.2 rc2 once fixes are merged for:
**Issues running glxgears (have a patch)
**Failure to boot on arrowlake platform (have a patch)
**genericarm64 has getty issues on some hardware platforms (no patch)
*YP 4.0.26 was released
*YP 5.0.9 is in QA
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*The mesa/llvm change has broken meta-clang causing autobuilder failures
*A recently merged wic test has intermittent failures
*Pending patches cause further breakage in various layers (e.g. qemu class change)
*Various other upgrades and fixes were merged to master

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2746 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1064)
**Patches in the Pending State: 140 (13%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 will have an rc2 built.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 was released.
*YP 5.0.9 is in QA.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 15th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 17th 10am GMT and Monday Apr. 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 rc1 has potential issues which may need an rc2:
**Issues running glxgears
**Failure to boot on arrowlake platform
**genericarm64 has getty issues on some hardware platforms
*YP 4.0.26 is out of QA and under review, likely to release
*Thanks to careful work, pending patches and overall total patches both decreased, thanks Alex.
*We upgraded mesa after some changes to the llvm build, thanks Dimitry.
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*We can now mark up python function variable dependencies using decorators, thanks Joshua.
*The bitbake whitespace change for assignment operators is ready to merge as we believe all autobuilder tested layers have updated.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1080)
**Patches in the Pending State: 144 (14%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 is in review.
*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.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.302 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 8th, 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:''' 
*Bug Triage meeting - Thursday Apr. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 10th 10am GMT and Monday Apr. 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.1.4 was released
*YP 5.2 rc1 is in QA
*YP 4.0.26 is ready for QA
*While 5.2 is in testing, master has continued to take patches which are ready.
*We are aiming to add more tag entries to SRC_URI for git SRCREV based recipes, please keep this in mind during upgrades.
*Some further analysis on the pseudo bug was posted
*There is a proposed whitespace syntax change with a pending bitbake patch to improve some consistency issues in formatting which can affect variable assignment.
*YP 5.3 Proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been separated from the clone servers so load spikes should only now impact the web interface.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2781) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1080)
**Patches in the Pending State: 167 (15%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.1.4 is released.
*YP 4.0.26 is ready for QA.
*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 

== Yocto Project Weekly Status Apr. 1st, 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:''' 
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1.4 is due for release
*Our first release candidate for YP 5.2 is ready for QA
*The walnascar branches have diverged from master
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 was released.
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.0.8 was released.
*YP 5.1.4 is ready for release.
*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 

== Yocto Project Weekly Status Mar. 25th, 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:''' 
*Bug Triage meeting - Thursday Mar. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 is due to be released
*YP 5.0.8 is due to be released
*YP 5.1.4 is in QA
*We are at feature freeze for YP 5.2 with our first rc build next week
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*SRC_URI entries for git now support tag verification against a specified source revision
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2801 (last week 2786) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1049)
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is ready for release.
*YP 5.1.4 is in QA.
*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 

== Yocto Project Weekly Status Mar. 18th, 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:''' 
*Bug Triage meeting Thursday Mar. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M3 has been through QA with one issue found
*YP 5.0.8 is in 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.
*Welcome improvements on syncing an sstate cache with a hash equivalence server were merged allowing more efficient hash equivalence server database cleanup, thanks!
*Bitbake python function library files were not always being cached correctly in bitbake’s parse cache, this was fixed.
*We started to merge gcc 15 fixes, particularly in native recipes as this will likely cause problems during the next release cycle with newer distro versions if we do not act.
*There were a number of minor version upgrades for bugs and CVE related issues.
*The recent annoying qemumips64 intermittent bug on the autobuilder looks to be a mips specific kernel issue which has been fixed upstream. We continue to wonder whether we should test mips/powerpc given the lack of interest in helping resolve issues.
*There are several fetcher changes pending including the ability to specify both a tag and a source revision.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2786 (last week 2816) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1049 (last week 1027)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is being reviewed.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is in 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 

== 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:''' 
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''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:''' 
*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.
*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.

'''Tracking Metrics:''' 
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*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:''' 
*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 

== Yocto Project Weekly Status Mar. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Mar. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 was released
*YP 5.1.3 is pending review
*We are now at feature freeze for YP 5.2
*Go was upgraded to 1.24, thanks to Jose and Hongxu for their work in making that happen and identifying the remaining reproducibility issue
*Rust upgrades to 1.83 and possibly 1.84 are close and we are aiming to include them in the release if possible
*The CVE/NVD situation is concerning enough we may delay the release build in the hope some improvements and process changes can be made.
*A cause of intermittent failures resulting in bitbake hangs was identified after 3 days of work from Richard (recursive events deadlocking)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*A new version of uninative compatible with glibc 2.41 was released.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2761) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1023)
**Patches in the Pending State: 170 (17%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 was released.
*YP 5.1.3 is in review.
*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 

== Yocto Project Weekly Status Feb. 25th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 is out of QA pending review
*YP 5.1.3 is in QA
*We are now 1 week from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*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/
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 is in review.
*YP 5.1.3 is in QA.
*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 

== Yocto Project Weekly Status Feb. 18th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.0.7 was released
*YP 4.0.25 is in QA
*We are now 2 weeks from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We plan to drop support for ifconfig now that the remaining usages in OE-Core have been patches to address them.
*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/ and in the weekly report last week. The situation remains unchanged.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2711 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1025)
**Patches in the Pending State: 172 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 was released.
*YP 4.0.25 is in QA.
*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 

== 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:''' 
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''Key Status/Updates:''' 
*YP 5.2 M2 was released
*YP 5.0.7 is under review and passed QA
*We are now 3 weeks from feature freeze for 5.2
*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’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**https://github.com/openembedded/openembedded-core/pulls
**https://github.com/openembedded/bitbake/pulls
*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.
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
*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/ :
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
***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:''' 
*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:''' 
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''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 

== Yocto Project Weekly Status Feb. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.24 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.0.7 was built and is ready for QA.
*We are now 4 weeks from feature freeze for 5.2
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*We plan to merge b4 configuration file support, thanks Quentin.
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Toolchain selection via virtual recipe specific providers was merged
*Patches for newer binutils, gdb and glibc are pending.
*The binutils upgrade removes gold linker support so that will be removed from core.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in review.
*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 4.0.24 was released.
*YP 5.0.7 is in QA.
*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 

== Yocto Project Weekly Status Jan. 28th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M2 was built and is in QA
*YP 5.0.7 was built and is ready for QA.
*YP 4.0.24 is in review.
*YP 5.1.2 was released
*Toolchain selection via virtual recipe specific providers was merged
*BB_CURRENT_MC behaviour was changed to default to an empty string rather than “default” to avoid complicating code to avoid bugs
*Bitbake-selftest was fixed to work with newly released git versions
*Problems were found with the gcc poison patches. Now they have been fixed, failures were found in some recipes showing host contamination issues
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2714 (last week 2724) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1024)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in QA.
*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 4.0.24 is ready for release.
*YP 5.1.2 was released.
*YP 5.0.7 is waiting for QA.
*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 

== Yocto Project Weekly Status Jan. 21st, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M1 was released, significantly delayed after several issues (see the release notes)
*YP 5.0.6 was released.
*YP 5.2 M2 is due to build this week, likely after the toolchain provider issues are resolved.
*YP 5.1.2 is under review for release
*YP 4.0.24 is still in QA
*After discussion and experimentation, support for toolchain selection via virtual/cross-cc is going to be added via a bitbake API, patches are under testing/review.
*Many good patches have been merged or are under review and close to merging, thanks all for the great work. Several do need small tweaks to get them over the line to the standard we need but it is great to see the variety and quality of the improvements.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2724 (last week 2763) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M1 was released.
*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 was released.
*YP 4.0.24 is in QA.
*YP 5.1.2 is ready for release.
*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 

== Yocto Project Weekly Status Jan. 14th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release 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)
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''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 175 (17%)]
*https://autobuilder.yocto.io/-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 is in QA.
*YP 5.1.2 is 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 

== Yocto Project Weekly Status Jan. 7th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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
**The issues are being investigated:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*YP 5.0.6 is ready to be released
*Feedback from Richard has now been given on the meta-clang merging patches which are not ready yet. Development work is needed to move this forward, a copy and paste into core isn’t enough and it will not merge without help from people.
*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.
*Patches using config fragment and include_all are being worked on in master-next for OE-Core.
*There is a proposed fix for some native class extension handling code bugs/issues however that fix creates new dependency problems and will require wider metadata changes.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2840 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1037 (last week 1046)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-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 in review.
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*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

2025 Yocto Project Weekly Status Archive

2025-12-23T15:54:56Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 16th, 2025 */

== Yocto Project Weekly Status Dec. 23th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan 10am GMT and Monday 5th Jan 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.32 has now been released!
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*Linux kernel 6.18 recipes are now available for testing but aren’t the default yet. Issues in OE-core are mostly resolved with some issues remaining for other layers. Wider testing is welcome as this will be the LTS kernel.
*Linux-libc-headers was also updated to 6.18, the 6.17 recipes were removed and 6.16 and 6.12 saw point release upgrades.
*Support for symlinking existing local repos with bitbake-setup has merged. There is ongoing work to simplify using a common hashequiv instance and sstate.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105).

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 2981) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1090 (last week 1083)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 was released.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 4.0.32 is in QA
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 is released.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 is in QA.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 was released
*YP 5.3 rc4 has passed QA and is under review
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in review for release.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 was released.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is due to be released
*YP 5.3 rc4 is built and due to enter QA
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in QA.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 25th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 27th 10am GMT and Monday Dec. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is under review for release.
*The final 5.3 build is still pending on fixing bugs from issues arising from the bitbake-setup changes. All other changes are now on hold for post release.
*We aim to build 5.3 when we have stable builds on the autobulder. Fixes from the changes around MACHINE/DISTRO conflict between conf/env and feature settings broke oe-selftest. The cooker feature change also exposed two existing bitbake *cache issues, particularly with memory resident bitbake. Those fixes merged but the fixes appear to be exposing further problems which are being investigated.
*Other potential changes that have been discussed but don’t have workable patches yet and are not going to block release::
**to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2953 (last week 2943) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1066)
**Patches in the Pending State: 152 (14%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 18th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 20th 10am GMT and Monday Nov. 24th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*The final 5.3 build is still pending on resolving some rough edges on bitbake-setup. The patches so far have made a huge difference, thanks everyone who helped!
*We aim to build 5.3 when the remaining identified issues with bitbake-setup are resolved:
**Improvements to the default build directory path (json format string?)
**Handling potential MACHINE/DISTRO conflict between conf/env and feature settings
**Comments to toolcfg.conf about how to change
**Mention "bitbake-config-build enable-fragment machine/XXX" in bitbake-setup output
**Remove/change broken template files from meta-yocto
*Other potential changes that have been discussed but don’t have workable patches yet:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2943 (last week 3048) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1066 (last week 1067)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 11th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 13th 10am GMT and Monday Nov. 17th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 was released
*YP 4.0.31 is due to be released
*We are not yet ready to build 5.3 as there are too many rough edges on bitbake-setup: https://lists.openembedded.org/g/openembedded-architecture/message/2199
*The documentation changes related to bitbake-setup merged, thanks to all who have helped on these.
*We are now no longer updating the poky master branch. The distro in meta-yocto remains. Long live poky.
*Toaster is now working with bitbake-setup, huge thanks to David Reyna for resolving the issues there.
*Upstream linux kernel end-of-life’d 6.16 but we can’t get 6.17 working fully so we’ll be releasing with 6.16 and removing the 6.17 recipes (merged in error).
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.
*We removed tcp-wrappers from OE-Core. It was late in but this should have happened long ago and if anyone is using it, you probably shouldn’t be!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3048 (last week 3103) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1098)
**Patches in the Pending State: 175 (16%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 was released.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 4.0.31 is in review for release.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 was released
*YP 5.3 M3 is due to be released
*YP 4.0.31 is in QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in review for release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 was released.
*YP 4.0.31 is in QA.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 is in QA
*YP 5.0.13 is under review for release
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 is in review for release.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 21st, 2025 ==
Current Dev Position: YP 5.3 M4 
Next Deadline: YP 5.3 M4 Build Date 2025-10-06 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday Oct. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 and 5.0.13 currently in QA.
*YP 5.2.4 has been released
*We’re at feature freeze for YP 5.3. Patches that will be accepted now have a higher bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve this issues!
*Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has been deleted. Many thanks to Deepesh and others at Wind River!. There’s a known regression building rust with clang which is being investigated.
*Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with 6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have to see as to whether we upgrade post-release.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3009 (last week 2904) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1096)
**Patches in the Pending State: 153 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 was released.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 14th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 16th 10am GMT and Monday Oct. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 is in QA.
*YP 5.2.4 is due to be released.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. The status is:
**llvm/clang split patches have merged
**bitbake-setup has merged
**the autobuilder has switched to use bitbake-setup for master builds
**there are build issues with bitbake-setup that have shown up with check-layer targets
**fixes for the reproducibility problem in perf from 6.16 are being tested
*“poky” as a combo-layer repository will soon no longer be needed or updated.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2904 (last week 2884) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 is ready for release.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 7th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is under review.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (patches ready and in testing)
**Merging of bitbake-setup
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is ready for release.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 30th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 2nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 30th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 2nd 10am GMT and Monday Oct. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is under review for release
*YP 5.2.4 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (currently blocked by uninative issues with llvm static libs)
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2854 (last week 2846) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1105)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is ready for release.
*YP 5.2.4 is in QA.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 23rd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 25th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 23rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 25th 10am GMT and Monday Sept. 29th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still aim to merge before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2846 (last week 2828) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1105 (last week 1112)
**Patches in the Pending State: 154 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is in QA.
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 16th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 18th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 16th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 18th 10am GMT and Monday Sept. 22nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*We have now updated to the 6.16 linux kernel
*There are clang/llvm performance improvements we plan to merge before building 5.3 (Thanks Ross!)
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2828 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1112 (last week 1111)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 is due to be released.
*YP 5.0.12 is due to be released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*We aim to merge bitbake-setup before building 5.3 M3
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is being reviewed for release.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 2nd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 4th 10am GMT and Monday Sept. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*RP is on holiday this week so should not be working
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA
*YP 5.3 M3 is due to build shortly (and is feature freeze)
*Linux 6.16 has been integrated but is currently not the default
*Patches continue to merge into master for upgrades and fixes until M3 is built
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*The Embedded Linux Conference was a success, with lots of Yocto-related talks being full to capacity. The OpenEmbedded and Yocto Project mini conferences were well attended and very interesting. Thanks to everyone who attended and made it a great event!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2845 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1096)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 26th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 28th 10am GMT and Monday Sept. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 was released
*YP 5.2.3 is in QA
*YP 5.0.12 is waiting for QA
*YP 5.3 M3 is due to build in one week (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays and conferences.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A 6.16 kernel recipe is available but we haven’t switched to it yet
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2878) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 was released.
*YP 5.2.3 is in QA.
*YP 5.0.12 is waiting for QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 19th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 19th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 21st 10am GMT and Monday Aug. 25th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 is due to be released
*YP 5.2.3 is in QA
*YP 5.3 M3 is due to build in two weeks (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Lttng component upgrades merged (babeltrace2 python enabling, lttng-modules, lttng-ust and lttng-tools) after several issues were resolved, particularly ptest failures.
*The kernel upgrade to 6.16 is under development. The libc-headers merged and is no longer blocked on lttng due to the upgrades above.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*For M3, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2848 (last week 2838) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is ready release.
*YP 5.2.3 is in QA.
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 12th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 14th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 12th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 14th 10am GMT and Monday Aug. 18th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 was released
*YP 4.0.29 is in QA
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*Images are now .zst compressed by default
*Bitbake variable “filter” support merged, which is useful to make class extension internals (and hence parse time) more efficient.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Glibc was upgraded to 2.42 with a new uninative added for the new version
*The kernel upgrade to 6.16 is blocked on lttng-modules which doesn’t support the new kernel version yet.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2838 (last week 2841) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 was released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is in QA.
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 5th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 7th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 5th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 7th 10am GMT and Monday Aug. 11th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*xz is now a required host tool
*Patches are proposed to change the default images to be .zst compressed since these work better for releases and sharing
*Compressed images have implications for runqemu which needs to be run in snapshot mode to boot them
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2841 (last week 2826) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is to be released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 29th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 31st 10am GMT and Monday Aug. 4th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 rc2 is in QA
*YP 5.0.11 was released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The lldb reproducibility regression was resolved, thanks!
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress but nuch work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2826 (last week 2799) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is in QA.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.11 was released.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 22nd, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 24th 10am GMT and Monday July 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build this week.
*YP 5.2.2 was released
*YP 5.0.11 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*We have a reproducibility regression in lldb which needs fixing urgently due to CI failures.
*We were able to root cause and resolve the 5.3 M1 QA reported gtk-play regression.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X merged, thanks to everyone who helped with fixes.
*Fixes for bitbake for python 3.14 around multiprocessing have been proposed. There are also bitbake profiling fixes for python 3.12+ and some small performance tweaks.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2799 (last week 2824) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1099)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.2 was released.
*YP 5.0.11 is ready for release.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 15th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 17th 10am GMT and Monday July 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build next week however we still need to look into and fix the issue found in M1: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*Help in debugging and fixing this would be very welcome.
*YP 5.2.2 is due to be released.
*YP 5.0.11 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. Patches from Ross start to split up the clang build and helped with a 5% speed improvement, thanks!
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X is ready to merge for core. The fixes to meta-openembedded are much appreciated.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2824 (last week 2800) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 was released.
*YP 5.2.2 is ready for release.
*YP 5.0.11 is in QA.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 8th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 10th 10am GMT and Monday July 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 was released. We still need to look into and fix the issue found: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is due to be released.
*YP 5.2.2 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*There are problems with building native recipes with clang on the autobuilder which are suggesting deeper issues in our gcc files layout.
*A fix for a rare parsing hang has merged and some tweaks to the parsing queueing process are under discussion.
*cmake 4.X is ready to merge for code but is causing significant (~100 recipes) breakage in meta-openembedded. We will hold off a short while but this will merge soon. Khem needs help to fix the recipes there.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 3)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2800 (last week 2770) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 was released.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is ready for release.
*YP 5.2.2 is in QA.
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is in QA.
*Patches continue to merge into master for upgrades and fixes.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*The clang build time and size increases continue to cause significant concern.
*Patches to improve gomod support in devtool merged.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 is ready for release.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 24th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
*To support this, the layer series was updated to whinlatter in core.
*The clang build time and size increases continue to cause significant concern.
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
*OE-Core is adopting the use of glvnd for libGL abstraction
*The initial RISC-V tune changes merged
*Support for distro/machine selection with builtin fragments was added.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 in QSA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 17th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 19th 10am GMT and Monday June 23rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.10 was released
*YP 5.3 M1 is due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection patches have merged
*For M2, the following changes have been mentioned as possibilities:
**Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
**bitbake-setup
**bitbake config fragment support for distro/machine
**wic split from OE-Core
**RISC-V tune changes
**go/gomod fetcher changes

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2777 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1084 (last week 1089)
**Patches in the Pending State: 158 (15%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.10 was released.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 10th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June 16th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 were released.
*YP 5.0.10 is due to be released.
*YP 5.3 M1 is now due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*Patches were sent out for a proposed toolchain selection mechanism implementation, feedback/review is welcome.
*Icecc.bbclass was removed.
*lz4 was removed from HOSTTOOLS as it was unneeded.
*Fitimage restructuring was merged, thanks Adrian.
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder so far, huge thanks to Michael Halstead for working on this.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2740 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1089)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 was released.
*YP 5.2.1 was released.
*YP 5.0.10 is ready for release.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 3rd, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 5th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 3rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 5th 10am GMT and Monday June 9th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 are due to be released.
*YP 5.0.10 is in QA.
*YP 5.3 M1 is one weeks away
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection mechanism is proving challenging as both the toolchain inherit and class extensions like native both need to happen ‘last’ and both involve overrides that are involved in deferred inherits. This issue may need bitbake changes to resolve.
*Should we drop icecc.bbclass and let someone step up and maintain it in its own layer?
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2803) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1088)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is out for review.
*YP 5.0.10 is in QA.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 27th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 29th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 27th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 29th 10am GMT and Monday June 2nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in under review for release
*YP 5.2.1 is in QA
*YP 5.3 M1 is two weeks away
*Patches continue to merge into master for upgrades and fixes.
*Further pieces of the clang changes have merged.
*There is a potential pending change to wic to rename plugins, changing “-” to “_”, feedback welcome on if/how we should handle this as it could be invasive in impact.
*The clang build time and size increases continue to cause significant concern.
*fitimage changes from Adrian are nearly ready to merge once two issues have been resolved.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2803 (last week 2813) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1088 (last week 1096)
**Patches in the Pending State: 157 (14%) [last week 158 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is in QA.
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 20th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in QA
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*musl-qemuarm64 was also added to default testing
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*Many good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is in QA.
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 13th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 15th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 13th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 15th 10am GMT and Monday May 19th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 was released
*We’re happy to announce that RISC-V is becoming a officially supported architecture for Yocto Project: https://riscv.org/riscv-news/2025/05/risc-v-international-and-the-rise-project-join-forces-for-yocto-project-support/
**Thanks to all who helped make this happen!
*Patches merged to switch pseudo from a directory exclusion list to a directory inclusion list. This change has long been requested but is now working and merged.
*The clang merge caused significant build time increases (nearly double) as well as image size increases, all of which we need analysis to try and mitigate if possible.
*Qemu changes upstream mean running it on 32 bit hosts may soon not be possible. 64 bit emulation on 32 bit hosts has already been dropped.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Many other good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2791 (last week 2753) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1104 (last week 1075)
**Patches in the Pending State: 159 (14%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 was released.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 6th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 8th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 6th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 8th 10am GMT and Monday May 12th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 was released
*YP 5.2 rc2 is pending release and the rc1 issues were fixed
*The gcc 15 upgrade merged
*We merged the clang recipe into oe-core replacing llvm. There are further tweaks and improvements pending but this gives us a baseline to improve upon.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. Layers including meta-openembedded will need updating to avoid these accesses.
*Many other good upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2753 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1075 (last week 1071)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in review for release.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 was released.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 29th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 1st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 1st 10am GMT and Monday May 5th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 is pending release.
*YP 5.2 rc2 is in QA.
*We have fixes/workarounds merged for the most frequent recent autobuilder issues apart from the clang problem after the mesa merge and CDN issue (which is being worked on).
*Patches continue to merge into master as review/time/testing allows. We are seeing a high number of failures in incoming patches which take time to resolve.
*The gcc 15 upgrade is close to ready to merge but there are failures in layers outside core.
*The clang/llvm recipe merge patch series is now mostly passing autobuilder testing and would step us closer to the meta-clang merge. Review help appreciated.
*Various other upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2746) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1071 (last week 1068)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 rc2 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 is ready for release.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 22rd, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 22rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 24th 10am GMT and Monday Apr. 28th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*We plan to build YP 5.2 rc2 once fixes are merged for:
**Issues running glxgears (have a patch)
**Failure to boot on arrowlake platform (have a patch)
**genericarm64 has getty issues on some hardware platforms (no patch)
*YP 4.0.26 was released
*YP 5.0.9 is in QA
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*The mesa/llvm change has broken meta-clang causing autobuilder failures
*A recently merged wic test has intermittent failures
*Pending patches cause further breakage in various layers (e.g. qemu class change)
*Various other upgrades and fixes were merged to master

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2746 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1064)
**Patches in the Pending State: 140 (13%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 will have an rc2 built.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 was released.
*YP 5.0.9 is in QA.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 15th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 17th 10am GMT and Monday Apr. 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 rc1 has potential issues which may need an rc2:
**Issues running glxgears
**Failure to boot on arrowlake platform
**genericarm64 has getty issues on some hardware platforms
*YP 4.0.26 is out of QA and under review, likely to release
*Thanks to careful work, pending patches and overall total patches both decreased, thanks Alex.
*We upgraded mesa after some changes to the llvm build, thanks Dimitry.
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*We can now mark up python function variable dependencies using decorators, thanks Joshua.
*The bitbake whitespace change for assignment operators is ready to merge as we believe all autobuilder tested layers have updated.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1080)
**Patches in the Pending State: 144 (14%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 is in review.
*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.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.302 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 8th, 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:''' 
*Bug Triage meeting - Thursday Apr. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 10th 10am GMT and Monday Apr. 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.1.4 was released
*YP 5.2 rc1 is in QA
*YP 4.0.26 is ready for QA
*While 5.2 is in testing, master has continued to take patches which are ready.
*We are aiming to add more tag entries to SRC_URI for git SRCREV based recipes, please keep this in mind during upgrades.
*Some further analysis on the pseudo bug was posted
*There is a proposed whitespace syntax change with a pending bitbake patch to improve some consistency issues in formatting which can affect variable assignment.
*YP 5.3 Proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been separated from the clone servers so load spikes should only now impact the web interface.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2781) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1080)
**Patches in the Pending State: 167 (15%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.1.4 is released.
*YP 4.0.26 is ready for QA.
*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 

== Yocto Project Weekly Status Apr. 1st, 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:''' 
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1.4 is due for release
*Our first release candidate for YP 5.2 is ready for QA
*The walnascar branches have diverged from master
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 was released.
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.0.8 was released.
*YP 5.1.4 is ready for release.
*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 

== Yocto Project Weekly Status Mar. 25th, 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:''' 
*Bug Triage meeting - Thursday Mar. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 is due to be released
*YP 5.0.8 is due to be released
*YP 5.1.4 is in QA
*We are at feature freeze for YP 5.2 with our first rc build next week
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*SRC_URI entries for git now support tag verification against a specified source revision
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2801 (last week 2786) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1049)
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is ready for release.
*YP 5.1.4 is in QA.
*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 

== Yocto Project Weekly Status Mar. 18th, 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:''' 
*Bug Triage meeting Thursday Mar. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M3 has been through QA with one issue found
*YP 5.0.8 is in 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.
*Welcome improvements on syncing an sstate cache with a hash equivalence server were merged allowing more efficient hash equivalence server database cleanup, thanks!
*Bitbake python function library files were not always being cached correctly in bitbake’s parse cache, this was fixed.
*We started to merge gcc 15 fixes, particularly in native recipes as this will likely cause problems during the next release cycle with newer distro versions if we do not act.
*There were a number of minor version upgrades for bugs and CVE related issues.
*The recent annoying qemumips64 intermittent bug on the autobuilder looks to be a mips specific kernel issue which has been fixed upstream. We continue to wonder whether we should test mips/powerpc given the lack of interest in helping resolve issues.
*There are several fetcher changes pending including the ability to specify both a tag and a source revision.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2786 (last week 2816) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1049 (last week 1027)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is being reviewed.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is in 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 

== 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:''' 
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''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:''' 
*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.
*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.

'''Tracking Metrics:''' 
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*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:''' 
*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 

== Yocto Project Weekly Status Mar. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Mar. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 was released
*YP 5.1.3 is pending review
*We are now at feature freeze for YP 5.2
*Go was upgraded to 1.24, thanks to Jose and Hongxu for their work in making that happen and identifying the remaining reproducibility issue
*Rust upgrades to 1.83 and possibly 1.84 are close and we are aiming to include them in the release if possible
*The CVE/NVD situation is concerning enough we may delay the release build in the hope some improvements and process changes can be made.
*A cause of intermittent failures resulting in bitbake hangs was identified after 3 days of work from Richard (recursive events deadlocking)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*A new version of uninative compatible with glibc 2.41 was released.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2761) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1023)
**Patches in the Pending State: 170 (17%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 was released.
*YP 5.1.3 is in review.
*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 

== Yocto Project Weekly Status Feb. 25th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 is out of QA pending review
*YP 5.1.3 is in QA
*We are now 1 week from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*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/
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 is in review.
*YP 5.1.3 is in QA.
*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 

== Yocto Project Weekly Status Feb. 18th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.0.7 was released
*YP 4.0.25 is in QA
*We are now 2 weeks from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We plan to drop support for ifconfig now that the remaining usages in OE-Core have been patches to address them.
*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/ and in the weekly report last week. The situation remains unchanged.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2711 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1025)
**Patches in the Pending State: 172 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 was released.
*YP 4.0.25 is in QA.
*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 

== 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:''' 
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''Key Status/Updates:''' 
*YP 5.2 M2 was released
*YP 5.0.7 is under review and passed QA
*We are now 3 weeks from feature freeze for 5.2
*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’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**https://github.com/openembedded/openembedded-core/pulls
**https://github.com/openembedded/bitbake/pulls
*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.
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
*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/ :
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
***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:''' 
*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:''' 
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''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 

== Yocto Project Weekly Status Feb. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.24 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.0.7 was built and is ready for QA.
*We are now 4 weeks from feature freeze for 5.2
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*We plan to merge b4 configuration file support, thanks Quentin.
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Toolchain selection via virtual recipe specific providers was merged
*Patches for newer binutils, gdb and glibc are pending.
*The binutils upgrade removes gold linker support so that will be removed from core.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in review.
*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 4.0.24 was released.
*YP 5.0.7 is in QA.
*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 

== Yocto Project Weekly Status Jan. 28th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M2 was built and is in QA
*YP 5.0.7 was built and is ready for QA.
*YP 4.0.24 is in review.
*YP 5.1.2 was released
*Toolchain selection via virtual recipe specific providers was merged
*BB_CURRENT_MC behaviour was changed to default to an empty string rather than “default” to avoid complicating code to avoid bugs
*Bitbake-selftest was fixed to work with newly released git versions
*Problems were found with the gcc poison patches. Now they have been fixed, failures were found in some recipes showing host contamination issues
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2714 (last week 2724) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1024)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in QA.
*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 4.0.24 is ready for release.
*YP 5.1.2 was released.
*YP 5.0.7 is waiting for QA.
*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 

== Yocto Project Weekly Status Jan. 21st, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M1 was released, significantly delayed after several issues (see the release notes)
*YP 5.0.6 was released.
*YP 5.2 M2 is due to build this week, likely after the toolchain provider issues are resolved.
*YP 5.1.2 is under review for release
*YP 4.0.24 is still in QA
*After discussion and experimentation, support for toolchain selection via virtual/cross-cc is going to be added via a bitbake API, patches are under testing/review.
*Many good patches have been merged or are under review and close to merging, thanks all for the great work. Several do need small tweaks to get them over the line to the standard we need but it is great to see the variety and quality of the improvements.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2724 (last week 2763) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M1 was released.
*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 was released.
*YP 4.0.24 is in QA.
*YP 5.1.2 is ready for release.
*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 

== Yocto Project Weekly Status Jan. 14th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release 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)
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''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 175 (17%)]
*https://autobuilder.yocto.io/-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 is in QA.
*YP 5.1.2 is 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 

== Yocto Project Weekly Status Jan. 7th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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
**The issues are being investigated:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*YP 5.0.6 is ready to be released
*Feedback from Richard has now been given on the meta-clang merging patches which are not ready yet. Development work is needed to move this forward, a copy and paste into core isn’t enough and it will not merge without help from people.
*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.
*Patches using config fragment and include_all are being worked on in master-next for OE-Core.
*There is a proposed fix for some native class extension handling code bugs/issues however that fix creates new dependency problems and will require wider metadata changes.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2840 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1037 (last week 1046)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-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 in review.
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*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

2025 Yocto Project Weekly Status Archive

2025-12-23T15:54:41Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 16th, 2025 */

== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday 8th Jan 10am GMT and Monday 5th Jan 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.32 has now been released!
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*Linux kernel 6.18 recipes are now available for testing but aren’t the default yet. Issues in OE-core are mostly resolved with some issues remaining for other layers. Wider testing is welcome as this will be the LTS kernel.
*Linux-libc-headers was also updated to 6.18, the 6.17 recipes were removed and 6.16 and 6.12 saw point release upgrades.
*Support for symlinking existing local repos with bitbake-setup has merged. There is ongoing work to simplify using a common hashequiv instance and sstate.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We will be entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved (https://bugzilla.yoctoproject.org/show_bug.cgi?id=16105).

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 2981) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1090 (last week 1083)
**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 was released.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 4.0.32 is in QA
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 is released.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 is in QA.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 was released
*YP 5.3 rc4 has passed QA and is under review
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in review for release.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 was released.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is due to be released
*YP 5.3 rc4 is built and due to enter QA
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in QA.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 25th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 27th 10am GMT and Monday Dec. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is under review for release.
*The final 5.3 build is still pending on fixing bugs from issues arising from the bitbake-setup changes. All other changes are now on hold for post release.
*We aim to build 5.3 when we have stable builds on the autobulder. Fixes from the changes around MACHINE/DISTRO conflict between conf/env and feature settings broke oe-selftest. The cooker feature change also exposed two existing bitbake *cache issues, particularly with memory resident bitbake. Those fixes merged but the fixes appear to be exposing further problems which are being investigated.
*Other potential changes that have been discussed but don’t have workable patches yet and are not going to block release::
**to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2953 (last week 2943) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1066)
**Patches in the Pending State: 152 (14%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 18th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 20th 10am GMT and Monday Nov. 24th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*The final 5.3 build is still pending on resolving some rough edges on bitbake-setup. The patches so far have made a huge difference, thanks everyone who helped!
*We aim to build 5.3 when the remaining identified issues with bitbake-setup are resolved:
**Improvements to the default build directory path (json format string?)
**Handling potential MACHINE/DISTRO conflict between conf/env and feature settings
**Comments to toolcfg.conf about how to change
**Mention "bitbake-config-build enable-fragment machine/XXX" in bitbake-setup output
**Remove/change broken template files from meta-yocto
*Other potential changes that have been discussed but don’t have workable patches yet:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2943 (last week 3048) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1066 (last week 1067)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 11th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 13th 10am GMT and Monday Nov. 17th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 was released
*YP 4.0.31 is due to be released
*We are not yet ready to build 5.3 as there are too many rough edges on bitbake-setup: https://lists.openembedded.org/g/openembedded-architecture/message/2199
*The documentation changes related to bitbake-setup merged, thanks to all who have helped on these.
*We are now no longer updating the poky master branch. The distro in meta-yocto remains. Long live poky.
*Toaster is now working with bitbake-setup, huge thanks to David Reyna for resolving the issues there.
*Upstream linux kernel end-of-life’d 6.16 but we can’t get 6.17 working fully so we’ll be releasing with 6.16 and removing the 6.17 recipes (merged in error).
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.
*We removed tcp-wrappers from OE-Core. It was late in but this should have happened long ago and if anyone is using it, you probably shouldn’t be!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3048 (last week 3103) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1098)
**Patches in the Pending State: 175 (16%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 was released.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 4.0.31 is in review for release.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 was released
*YP 5.3 M3 is due to be released
*YP 4.0.31 is in QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in review for release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 was released.
*YP 4.0.31 is in QA.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 is in QA
*YP 5.0.13 is under review for release
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 is in review for release.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 21st, 2025 ==
Current Dev Position: YP 5.3 M4 
Next Deadline: YP 5.3 M4 Build Date 2025-10-06 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday Oct. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 and 5.0.13 currently in QA.
*YP 5.2.4 has been released
*We’re at feature freeze for YP 5.3. Patches that will be accepted now have a higher bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve this issues!
*Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has been deleted. Many thanks to Deepesh and others at Wind River!. There’s a known regression building rust with clang which is being investigated.
*Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with 6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have to see as to whether we upgrade post-release.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3009 (last week 2904) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1096)
**Patches in the Pending State: 153 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 was released.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 14th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 16th 10am GMT and Monday Oct. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 is in QA.
*YP 5.2.4 is due to be released.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. The status is:
**llvm/clang split patches have merged
**bitbake-setup has merged
**the autobuilder has switched to use bitbake-setup for master builds
**there are build issues with bitbake-setup that have shown up with check-layer targets
**fixes for the reproducibility problem in perf from 6.16 are being tested
*“poky” as a combo-layer repository will soon no longer be needed or updated.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2904 (last week 2884) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 is ready for release.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 7th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is under review.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (patches ready and in testing)
**Merging of bitbake-setup
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is ready for release.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 30th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 2nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 30th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 2nd 10am GMT and Monday Oct. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is under review for release
*YP 5.2.4 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (currently blocked by uninative issues with llvm static libs)
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2854 (last week 2846) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1105)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is ready for release.
*YP 5.2.4 is in QA.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 23rd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 25th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 23rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 25th 10am GMT and Monday Sept. 29th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still aim to merge before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2846 (last week 2828) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1105 (last week 1112)
**Patches in the Pending State: 154 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is in QA.
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 16th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 18th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 16th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 18th 10am GMT and Monday Sept. 22nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*We have now updated to the 6.16 linux kernel
*There are clang/llvm performance improvements we plan to merge before building 5.3 (Thanks Ross!)
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2828 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1112 (last week 1111)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 is due to be released.
*YP 5.0.12 is due to be released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*We aim to merge bitbake-setup before building 5.3 M3
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is being reviewed for release.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 2nd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 4th 10am GMT and Monday Sept. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*RP is on holiday this week so should not be working
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA
*YP 5.3 M3 is due to build shortly (and is feature freeze)
*Linux 6.16 has been integrated but is currently not the default
*Patches continue to merge into master for upgrades and fixes until M3 is built
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*The Embedded Linux Conference was a success, with lots of Yocto-related talks being full to capacity. The OpenEmbedded and Yocto Project mini conferences were well attended and very interesting. Thanks to everyone who attended and made it a great event!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2845 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1096)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 26th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 28th 10am GMT and Monday Sept. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 was released
*YP 5.2.3 is in QA
*YP 5.0.12 is waiting for QA
*YP 5.3 M3 is due to build in one week (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays and conferences.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A 6.16 kernel recipe is available but we haven’t switched to it yet
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2878) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 was released.
*YP 5.2.3 is in QA.
*YP 5.0.12 is waiting for QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 19th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 19th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 21st 10am GMT and Monday Aug. 25th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 is due to be released
*YP 5.2.3 is in QA
*YP 5.3 M3 is due to build in two weeks (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Lttng component upgrades merged (babeltrace2 python enabling, lttng-modules, lttng-ust and lttng-tools) after several issues were resolved, particularly ptest failures.
*The kernel upgrade to 6.16 is under development. The libc-headers merged and is no longer blocked on lttng due to the upgrades above.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*For M3, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2848 (last week 2838) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is ready release.
*YP 5.2.3 is in QA.
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 12th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 14th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 12th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 14th 10am GMT and Monday Aug. 18th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 was released
*YP 4.0.29 is in QA
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*Images are now .zst compressed by default
*Bitbake variable “filter” support merged, which is useful to make class extension internals (and hence parse time) more efficient.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Glibc was upgraded to 2.42 with a new uninative added for the new version
*The kernel upgrade to 6.16 is blocked on lttng-modules which doesn’t support the new kernel version yet.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2838 (last week 2841) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 was released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is in QA.
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 5th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 7th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 5th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 7th 10am GMT and Monday Aug. 11th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*xz is now a required host tool
*Patches are proposed to change the default images to be .zst compressed since these work better for releases and sharing
*Compressed images have implications for runqemu which needs to be run in snapshot mode to boot them
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2841 (last week 2826) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is to be released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 29th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 31st 10am GMT and Monday Aug. 4th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 rc2 is in QA
*YP 5.0.11 was released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The lldb reproducibility regression was resolved, thanks!
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress but nuch work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2826 (last week 2799) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is in QA.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.11 was released.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 22nd, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 24th 10am GMT and Monday July 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build this week.
*YP 5.2.2 was released
*YP 5.0.11 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*We have a reproducibility regression in lldb which needs fixing urgently due to CI failures.
*We were able to root cause and resolve the 5.3 M1 QA reported gtk-play regression.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X merged, thanks to everyone who helped with fixes.
*Fixes for bitbake for python 3.14 around multiprocessing have been proposed. There are also bitbake profiling fixes for python 3.12+ and some small performance tweaks.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2799 (last week 2824) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1099)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.2 was released.
*YP 5.0.11 is ready for release.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 15th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 17th 10am GMT and Monday July 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build next week however we still need to look into and fix the issue found in M1: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*Help in debugging and fixing this would be very welcome.
*YP 5.2.2 is due to be released.
*YP 5.0.11 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. Patches from Ross start to split up the clang build and helped with a 5% speed improvement, thanks!
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X is ready to merge for core. The fixes to meta-openembedded are much appreciated.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2824 (last week 2800) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 was released.
*YP 5.2.2 is ready for release.
*YP 5.0.11 is in QA.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 8th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 10th 10am GMT and Monday July 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 was released. We still need to look into and fix the issue found: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is due to be released.
*YP 5.2.2 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*There are problems with building native recipes with clang on the autobuilder which are suggesting deeper issues in our gcc files layout.
*A fix for a rare parsing hang has merged and some tweaks to the parsing queueing process are under discussion.
*cmake 4.X is ready to merge for code but is causing significant (~100 recipes) breakage in meta-openembedded. We will hold off a short while but this will merge soon. Khem needs help to fix the recipes there.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 3)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2800 (last week 2770) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 was released.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is ready for release.
*YP 5.2.2 is in QA.
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is in QA.
*Patches continue to merge into master for upgrades and fixes.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*The clang build time and size increases continue to cause significant concern.
*Patches to improve gomod support in devtool merged.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 is ready for release.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 24th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
*To support this, the layer series was updated to whinlatter in core.
*The clang build time and size increases continue to cause significant concern.
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
*OE-Core is adopting the use of glvnd for libGL abstraction
*The initial RISC-V tune changes merged
*Support for distro/machine selection with builtin fragments was added.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 in QSA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 17th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 19th 10am GMT and Monday June 23rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.10 was released
*YP 5.3 M1 is due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection patches have merged
*For M2, the following changes have been mentioned as possibilities:
**Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
**bitbake-setup
**bitbake config fragment support for distro/machine
**wic split from OE-Core
**RISC-V tune changes
**go/gomod fetcher changes

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2777 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1084 (last week 1089)
**Patches in the Pending State: 158 (15%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.10 was released.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 10th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June 16th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 were released.
*YP 5.0.10 is due to be released.
*YP 5.3 M1 is now due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*Patches were sent out for a proposed toolchain selection mechanism implementation, feedback/review is welcome.
*Icecc.bbclass was removed.
*lz4 was removed from HOSTTOOLS as it was unneeded.
*Fitimage restructuring was merged, thanks Adrian.
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder so far, huge thanks to Michael Halstead for working on this.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2740 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1089)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 was released.
*YP 5.2.1 was released.
*YP 5.0.10 is ready for release.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 3rd, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 5th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 3rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 5th 10am GMT and Monday June 9th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 are due to be released.
*YP 5.0.10 is in QA.
*YP 5.3 M1 is one weeks away
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection mechanism is proving challenging as both the toolchain inherit and class extensions like native both need to happen ‘last’ and both involve overrides that are involved in deferred inherits. This issue may need bitbake changes to resolve.
*Should we drop icecc.bbclass and let someone step up and maintain it in its own layer?
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2803) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1088)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is out for review.
*YP 5.0.10 is in QA.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 27th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 29th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 27th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 29th 10am GMT and Monday June 2nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in under review for release
*YP 5.2.1 is in QA
*YP 5.3 M1 is two weeks away
*Patches continue to merge into master for upgrades and fixes.
*Further pieces of the clang changes have merged.
*There is a potential pending change to wic to rename plugins, changing “-” to “_”, feedback welcome on if/how we should handle this as it could be invasive in impact.
*The clang build time and size increases continue to cause significant concern.
*fitimage changes from Adrian are nearly ready to merge once two issues have been resolved.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2803 (last week 2813) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1088 (last week 1096)
**Patches in the Pending State: 157 (14%) [last week 158 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is in QA.
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 20th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in QA
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*musl-qemuarm64 was also added to default testing
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*Many good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is in QA.
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 13th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 15th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 13th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 15th 10am GMT and Monday May 19th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 was released
*We’re happy to announce that RISC-V is becoming a officially supported architecture for Yocto Project: https://riscv.org/riscv-news/2025/05/risc-v-international-and-the-rise-project-join-forces-for-yocto-project-support/
**Thanks to all who helped make this happen!
*Patches merged to switch pseudo from a directory exclusion list to a directory inclusion list. This change has long been requested but is now working and merged.
*The clang merge caused significant build time increases (nearly double) as well as image size increases, all of which we need analysis to try and mitigate if possible.
*Qemu changes upstream mean running it on 32 bit hosts may soon not be possible. 64 bit emulation on 32 bit hosts has already been dropped.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Many other good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2791 (last week 2753) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1104 (last week 1075)
**Patches in the Pending State: 159 (14%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 was released.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 6th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 8th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 6th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 8th 10am GMT and Monday May 12th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 was released
*YP 5.2 rc2 is pending release and the rc1 issues were fixed
*The gcc 15 upgrade merged
*We merged the clang recipe into oe-core replacing llvm. There are further tweaks and improvements pending but this gives us a baseline to improve upon.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. Layers including meta-openembedded will need updating to avoid these accesses.
*Many other good upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2753 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1075 (last week 1071)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in review for release.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 was released.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 29th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 1st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 1st 10am GMT and Monday May 5th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 is pending release.
*YP 5.2 rc2 is in QA.
*We have fixes/workarounds merged for the most frequent recent autobuilder issues apart from the clang problem after the mesa merge and CDN issue (which is being worked on).
*Patches continue to merge into master as review/time/testing allows. We are seeing a high number of failures in incoming patches which take time to resolve.
*The gcc 15 upgrade is close to ready to merge but there are failures in layers outside core.
*The clang/llvm recipe merge patch series is now mostly passing autobuilder testing and would step us closer to the meta-clang merge. Review help appreciated.
*Various other upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2746) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1071 (last week 1068)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 rc2 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 is ready for release.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 22rd, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 22rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 24th 10am GMT and Monday Apr. 28th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*We plan to build YP 5.2 rc2 once fixes are merged for:
**Issues running glxgears (have a patch)
**Failure to boot on arrowlake platform (have a patch)
**genericarm64 has getty issues on some hardware platforms (no patch)
*YP 4.0.26 was released
*YP 5.0.9 is in QA
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*The mesa/llvm change has broken meta-clang causing autobuilder failures
*A recently merged wic test has intermittent failures
*Pending patches cause further breakage in various layers (e.g. qemu class change)
*Various other upgrades and fixes were merged to master

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2746 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1064)
**Patches in the Pending State: 140 (13%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 will have an rc2 built.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 was released.
*YP 5.0.9 is in QA.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 15th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 17th 10am GMT and Monday Apr. 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 rc1 has potential issues which may need an rc2:
**Issues running glxgears
**Failure to boot on arrowlake platform
**genericarm64 has getty issues on some hardware platforms
*YP 4.0.26 is out of QA and under review, likely to release
*Thanks to careful work, pending patches and overall total patches both decreased, thanks Alex.
*We upgraded mesa after some changes to the llvm build, thanks Dimitry.
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*We can now mark up python function variable dependencies using decorators, thanks Joshua.
*The bitbake whitespace change for assignment operators is ready to merge as we believe all autobuilder tested layers have updated.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1080)
**Patches in the Pending State: 144 (14%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 is in review.
*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.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.302 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 8th, 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:''' 
*Bug Triage meeting - Thursday Apr. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 10th 10am GMT and Monday Apr. 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.1.4 was released
*YP 5.2 rc1 is in QA
*YP 4.0.26 is ready for QA
*While 5.2 is in testing, master has continued to take patches which are ready.
*We are aiming to add more tag entries to SRC_URI for git SRCREV based recipes, please keep this in mind during upgrades.
*Some further analysis on the pseudo bug was posted
*There is a proposed whitespace syntax change with a pending bitbake patch to improve some consistency issues in formatting which can affect variable assignment.
*YP 5.3 Proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been separated from the clone servers so load spikes should only now impact the web interface.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2781) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1080)
**Patches in the Pending State: 167 (15%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.1.4 is released.
*YP 4.0.26 is ready for QA.
*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 

== Yocto Project Weekly Status Apr. 1st, 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:''' 
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1.4 is due for release
*Our first release candidate for YP 5.2 is ready for QA
*The walnascar branches have diverged from master
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 was released.
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.0.8 was released.
*YP 5.1.4 is ready for release.
*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 

== Yocto Project Weekly Status Mar. 25th, 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:''' 
*Bug Triage meeting - Thursday Mar. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 is due to be released
*YP 5.0.8 is due to be released
*YP 5.1.4 is in QA
*We are at feature freeze for YP 5.2 with our first rc build next week
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*SRC_URI entries for git now support tag verification against a specified source revision
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2801 (last week 2786) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1049)
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is ready for release.
*YP 5.1.4 is in QA.
*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 

== Yocto Project Weekly Status Mar. 18th, 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:''' 
*Bug Triage meeting Thursday Mar. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M3 has been through QA with one issue found
*YP 5.0.8 is in 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.
*Welcome improvements on syncing an sstate cache with a hash equivalence server were merged allowing more efficient hash equivalence server database cleanup, thanks!
*Bitbake python function library files were not always being cached correctly in bitbake’s parse cache, this was fixed.
*We started to merge gcc 15 fixes, particularly in native recipes as this will likely cause problems during the next release cycle with newer distro versions if we do not act.
*There were a number of minor version upgrades for bugs and CVE related issues.
*The recent annoying qemumips64 intermittent bug on the autobuilder looks to be a mips specific kernel issue which has been fixed upstream. We continue to wonder whether we should test mips/powerpc given the lack of interest in helping resolve issues.
*There are several fetcher changes pending including the ability to specify both a tag and a source revision.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2786 (last week 2816) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1049 (last week 1027)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is being reviewed.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is in 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 

== 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:''' 
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''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:''' 
*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.
*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.

'''Tracking Metrics:''' 
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*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:''' 
*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 

== Yocto Project Weekly Status Mar. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Mar. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 was released
*YP 5.1.3 is pending review
*We are now at feature freeze for YP 5.2
*Go was upgraded to 1.24, thanks to Jose and Hongxu for their work in making that happen and identifying the remaining reproducibility issue
*Rust upgrades to 1.83 and possibly 1.84 are close and we are aiming to include them in the release if possible
*The CVE/NVD situation is concerning enough we may delay the release build in the hope some improvements and process changes can be made.
*A cause of intermittent failures resulting in bitbake hangs was identified after 3 days of work from Richard (recursive events deadlocking)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*A new version of uninative compatible with glibc 2.41 was released.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2761) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1023)
**Patches in the Pending State: 170 (17%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 was released.
*YP 5.1.3 is in review.
*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 

== Yocto Project Weekly Status Feb. 25th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 is out of QA pending review
*YP 5.1.3 is in QA
*We are now 1 week from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*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/
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 is in review.
*YP 5.1.3 is in QA.
*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 

== Yocto Project Weekly Status Feb. 18th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.0.7 was released
*YP 4.0.25 is in QA
*We are now 2 weeks from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We plan to drop support for ifconfig now that the remaining usages in OE-Core have been patches to address them.
*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/ and in the weekly report last week. The situation remains unchanged.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2711 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1025)
**Patches in the Pending State: 172 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 was released.
*YP 4.0.25 is in QA.
*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 

== 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:''' 
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''Key Status/Updates:''' 
*YP 5.2 M2 was released
*YP 5.0.7 is under review and passed QA
*We are now 3 weeks from feature freeze for 5.2
*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’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**https://github.com/openembedded/openembedded-core/pulls
**https://github.com/openembedded/bitbake/pulls
*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.
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
*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/ :
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
***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:''' 
*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:''' 
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''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 

== Yocto Project Weekly Status Feb. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.24 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.0.7 was built and is ready for QA.
*We are now 4 weeks from feature freeze for 5.2
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*We plan to merge b4 configuration file support, thanks Quentin.
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Toolchain selection via virtual recipe specific providers was merged
*Patches for newer binutils, gdb and glibc are pending.
*The binutils upgrade removes gold linker support so that will be removed from core.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in review.
*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 4.0.24 was released.
*YP 5.0.7 is in QA.
*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 

== Yocto Project Weekly Status Jan. 28th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M2 was built and is in QA
*YP 5.0.7 was built and is ready for QA.
*YP 4.0.24 is in review.
*YP 5.1.2 was released
*Toolchain selection via virtual recipe specific providers was merged
*BB_CURRENT_MC behaviour was changed to default to an empty string rather than “default” to avoid complicating code to avoid bugs
*Bitbake-selftest was fixed to work with newly released git versions
*Problems were found with the gcc poison patches. Now they have been fixed, failures were found in some recipes showing host contamination issues
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2714 (last week 2724) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1024)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in QA.
*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 4.0.24 is ready for release.
*YP 5.1.2 was released.
*YP 5.0.7 is waiting for QA.
*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 

== Yocto Project Weekly Status Jan. 21st, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M1 was released, significantly delayed after several issues (see the release notes)
*YP 5.0.6 was released.
*YP 5.2 M2 is due to build this week, likely after the toolchain provider issues are resolved.
*YP 5.1.2 is under review for release
*YP 4.0.24 is still in QA
*After discussion and experimentation, support for toolchain selection via virtual/cross-cc is going to be added via a bitbake API, patches are under testing/review.
*Many good patches have been merged or are under review and close to merging, thanks all for the great work. Several do need small tweaks to get them over the line to the standard we need but it is great to see the variety and quality of the improvements.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2724 (last week 2763) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M1 was released.
*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 was released.
*YP 4.0.24 is in QA.
*YP 5.1.2 is ready for release.
*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 

== Yocto Project Weekly Status Jan. 14th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release 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)
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''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 175 (17%)]
*https://autobuilder.yocto.io/-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 is in QA.
*YP 5.1.2 is 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 

== Yocto Project Weekly Status Jan. 7th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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
**The issues are being investigated:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*YP 5.0.6 is ready to be released
*Feedback from Richard has now been given on the meta-clang merging patches which are not ready yet. Development work is needed to move this forward, a copy and paste into core isn’t enough and it will not merge without help from people.
*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.
*Patches using config fragment and include_all are being worked on in master-next for OE-Core.
*There is a proposed fix for some native class extension handling code bugs/issues however that fix creates new dependency problems and will require wider metadata changes.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2840 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1037 (last week 1046)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-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 in review.
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*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

Weekly Status

2025-12-23T15:53:50Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 16th, 2025 */

2025 Yocto Project Weekly Status Archive

2025-12-16T15:51:54Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 9th, 2025 */

== Yocto Project Weekly Status Dec. 16th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 18th at 7:30 am PST, then Thursday 8th Jan 7:30am (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 18th 8 am PDT, then Tuesday 6th Jan 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 18th 10am GMT and Monday Dec. 22th 9am PDT, then Monday 5th January 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 was released, thanks to everyone who helped make it happen!
*YP 4.0.32 is in QA
*The project will be taking a break from our regular meetings from 24th December until 4th January for the holidays.
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 is released.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.32 is in QA.
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 6.0 M1 
Next Deadline: YP 6.0 M1 Build Date 2026-01-05 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 was released
*YP 5.3 rc4 has passed QA and is under review
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in review for release.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 was released.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is due to be released
*YP 5.3 rc4 is built and due to enter QA
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in QA.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 25th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 27th 10am GMT and Monday Dec. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is under review for release.
*The final 5.3 build is still pending on fixing bugs from issues arising from the bitbake-setup changes. All other changes are now on hold for post release.
*We aim to build 5.3 when we have stable builds on the autobulder. Fixes from the changes around MACHINE/DISTRO conflict between conf/env and feature settings broke oe-selftest. The cooker feature change also exposed two existing bitbake *cache issues, particularly with memory resident bitbake. Those fixes merged but the fixes appear to be exposing further problems which are being investigated.
*Other potential changes that have been discussed but don’t have workable patches yet and are not going to block release::
**to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2953 (last week 2943) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1066)
**Patches in the Pending State: 152 (14%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 18th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 20th 10am GMT and Monday Nov. 24th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*The final 5.3 build is still pending on resolving some rough edges on bitbake-setup. The patches so far have made a huge difference, thanks everyone who helped!
*We aim to build 5.3 when the remaining identified issues with bitbake-setup are resolved:
**Improvements to the default build directory path (json format string?)
**Handling potential MACHINE/DISTRO conflict between conf/env and feature settings
**Comments to toolcfg.conf about how to change
**Mention "bitbake-config-build enable-fragment machine/XXX" in bitbake-setup output
**Remove/change broken template files from meta-yocto
*Other potential changes that have been discussed but don’t have workable patches yet:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2943 (last week 3048) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1066 (last week 1067)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 11th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 13th 10am GMT and Monday Nov. 17th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 was released
*YP 4.0.31 is due to be released
*We are not yet ready to build 5.3 as there are too many rough edges on bitbake-setup: https://lists.openembedded.org/g/openembedded-architecture/message/2199
*The documentation changes related to bitbake-setup merged, thanks to all who have helped on these.
*We are now no longer updating the poky master branch. The distro in meta-yocto remains. Long live poky.
*Toaster is now working with bitbake-setup, huge thanks to David Reyna for resolving the issues there.
*Upstream linux kernel end-of-life’d 6.16 but we can’t get 6.17 working fully so we’ll be releasing with 6.16 and removing the 6.17 recipes (merged in error).
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.
*We removed tcp-wrappers from OE-Core. It was late in but this should have happened long ago and if anyone is using it, you probably shouldn’t be!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3048 (last week 3103) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1098)
**Patches in the Pending State: 175 (16%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 was released.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 4.0.31 is in review for release.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 was released
*YP 5.3 M3 is due to be released
*YP 4.0.31 is in QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in review for release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 was released.
*YP 4.0.31 is in QA.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 is in QA
*YP 5.0.13 is under review for release
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 is in review for release.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 21st, 2025 ==
Current Dev Position: YP 5.3 M4 
Next Deadline: YP 5.3 M4 Build Date 2025-10-06 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday Oct. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 and 5.0.13 currently in QA.
*YP 5.2.4 has been released
*We’re at feature freeze for YP 5.3. Patches that will be accepted now have a higher bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve this issues!
*Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has been deleted. Many thanks to Deepesh and others at Wind River!. There’s a known regression building rust with clang which is being investigated.
*Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with 6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have to see as to whether we upgrade post-release.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3009 (last week 2904) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1096)
**Patches in the Pending State: 153 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 was released.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 14th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 16th 10am GMT and Monday Oct. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 is in QA.
*YP 5.2.4 is due to be released.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. The status is:
**llvm/clang split patches have merged
**bitbake-setup has merged
**the autobuilder has switched to use bitbake-setup for master builds
**there are build issues with bitbake-setup that have shown up with check-layer targets
**fixes for the reproducibility problem in perf from 6.16 are being tested
*“poky” as a combo-layer repository will soon no longer be needed or updated.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2904 (last week 2884) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 is ready for release.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 7th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is under review.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (patches ready and in testing)
**Merging of bitbake-setup
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is ready for release.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 30th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 2nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 30th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 2nd 10am GMT and Monday Oct. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is under review for release
*YP 5.2.4 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (currently blocked by uninative issues with llvm static libs)
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2854 (last week 2846) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1105)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is ready for release.
*YP 5.2.4 is in QA.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 23rd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 25th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 23rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 25th 10am GMT and Monday Sept. 29th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still aim to merge before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2846 (last week 2828) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1105 (last week 1112)
**Patches in the Pending State: 154 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is in QA.
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 16th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 18th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 16th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 18th 10am GMT and Monday Sept. 22nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*We have now updated to the 6.16 linux kernel
*There are clang/llvm performance improvements we plan to merge before building 5.3 (Thanks Ross!)
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2828 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1112 (last week 1111)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 is due to be released.
*YP 5.0.12 is due to be released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*We aim to merge bitbake-setup before building 5.3 M3
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is being reviewed for release.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 2nd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 4th 10am GMT and Monday Sept. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*RP is on holiday this week so should not be working
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA
*YP 5.3 M3 is due to build shortly (and is feature freeze)
*Linux 6.16 has been integrated but is currently not the default
*Patches continue to merge into master for upgrades and fixes until M3 is built
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*The Embedded Linux Conference was a success, with lots of Yocto-related talks being full to capacity. The OpenEmbedded and Yocto Project mini conferences were well attended and very interesting. Thanks to everyone who attended and made it a great event!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2845 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1096)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 26th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 28th 10am GMT and Monday Sept. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 was released
*YP 5.2.3 is in QA
*YP 5.0.12 is waiting for QA
*YP 5.3 M3 is due to build in one week (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays and conferences.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A 6.16 kernel recipe is available but we haven’t switched to it yet
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2878) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 was released.
*YP 5.2.3 is in QA.
*YP 5.0.12 is waiting for QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 19th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 19th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 21st 10am GMT and Monday Aug. 25th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 is due to be released
*YP 5.2.3 is in QA
*YP 5.3 M3 is due to build in two weeks (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Lttng component upgrades merged (babeltrace2 python enabling, lttng-modules, lttng-ust and lttng-tools) after several issues were resolved, particularly ptest failures.
*The kernel upgrade to 6.16 is under development. The libc-headers merged and is no longer blocked on lttng due to the upgrades above.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*For M3, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2848 (last week 2838) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is ready release.
*YP 5.2.3 is in QA.
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 12th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 14th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 12th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 14th 10am GMT and Monday Aug. 18th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 was released
*YP 4.0.29 is in QA
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*Images are now .zst compressed by default
*Bitbake variable “filter” support merged, which is useful to make class extension internals (and hence parse time) more efficient.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Glibc was upgraded to 2.42 with a new uninative added for the new version
*The kernel upgrade to 6.16 is blocked on lttng-modules which doesn’t support the new kernel version yet.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2838 (last week 2841) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 was released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is in QA.
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 5th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 7th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 5th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 7th 10am GMT and Monday Aug. 11th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*xz is now a required host tool
*Patches are proposed to change the default images to be .zst compressed since these work better for releases and sharing
*Compressed images have implications for runqemu which needs to be run in snapshot mode to boot them
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2841 (last week 2826) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is to be released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 29th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 31st 10am GMT and Monday Aug. 4th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 rc2 is in QA
*YP 5.0.11 was released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The lldb reproducibility regression was resolved, thanks!
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress but nuch work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2826 (last week 2799) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is in QA.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.11 was released.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 22nd, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 24th 10am GMT and Monday July 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build this week.
*YP 5.2.2 was released
*YP 5.0.11 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*We have a reproducibility regression in lldb which needs fixing urgently due to CI failures.
*We were able to root cause and resolve the 5.3 M1 QA reported gtk-play regression.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X merged, thanks to everyone who helped with fixes.
*Fixes for bitbake for python 3.14 around multiprocessing have been proposed. There are also bitbake profiling fixes for python 3.12+ and some small performance tweaks.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2799 (last week 2824) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1099)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.2 was released.
*YP 5.0.11 is ready for release.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 15th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 17th 10am GMT and Monday July 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build next week however we still need to look into and fix the issue found in M1: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*Help in debugging and fixing this would be very welcome.
*YP 5.2.2 is due to be released.
*YP 5.0.11 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. Patches from Ross start to split up the clang build and helped with a 5% speed improvement, thanks!
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X is ready to merge for core. The fixes to meta-openembedded are much appreciated.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2824 (last week 2800) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 was released.
*YP 5.2.2 is ready for release.
*YP 5.0.11 is in QA.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 8th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 10th 10am GMT and Monday July 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 was released. We still need to look into and fix the issue found: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is due to be released.
*YP 5.2.2 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*There are problems with building native recipes with clang on the autobuilder which are suggesting deeper issues in our gcc files layout.
*A fix for a rare parsing hang has merged and some tweaks to the parsing queueing process are under discussion.
*cmake 4.X is ready to merge for code but is causing significant (~100 recipes) breakage in meta-openembedded. We will hold off a short while but this will merge soon. Khem needs help to fix the recipes there.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 3)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2800 (last week 2770) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 was released.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is ready for release.
*YP 5.2.2 is in QA.
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is in QA.
*Patches continue to merge into master for upgrades and fixes.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*The clang build time and size increases continue to cause significant concern.
*Patches to improve gomod support in devtool merged.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 is ready for release.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 24th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
*To support this, the layer series was updated to whinlatter in core.
*The clang build time and size increases continue to cause significant concern.
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
*OE-Core is adopting the use of glvnd for libGL abstraction
*The initial RISC-V tune changes merged
*Support for distro/machine selection with builtin fragments was added.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 in QSA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 17th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 19th 10am GMT and Monday June 23rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.10 was released
*YP 5.3 M1 is due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection patches have merged
*For M2, the following changes have been mentioned as possibilities:
**Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
**bitbake-setup
**bitbake config fragment support for distro/machine
**wic split from OE-Core
**RISC-V tune changes
**go/gomod fetcher changes

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2777 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1084 (last week 1089)
**Patches in the Pending State: 158 (15%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.10 was released.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 10th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June 16th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 were released.
*YP 5.0.10 is due to be released.
*YP 5.3 M1 is now due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*Patches were sent out for a proposed toolchain selection mechanism implementation, feedback/review is welcome.
*Icecc.bbclass was removed.
*lz4 was removed from HOSTTOOLS as it was unneeded.
*Fitimage restructuring was merged, thanks Adrian.
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder so far, huge thanks to Michael Halstead for working on this.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2740 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1089)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 was released.
*YP 5.2.1 was released.
*YP 5.0.10 is ready for release.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 3rd, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 5th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 3rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 5th 10am GMT and Monday June 9th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 are due to be released.
*YP 5.0.10 is in QA.
*YP 5.3 M1 is one weeks away
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection mechanism is proving challenging as both the toolchain inherit and class extensions like native both need to happen ‘last’ and both involve overrides that are involved in deferred inherits. This issue may need bitbake changes to resolve.
*Should we drop icecc.bbclass and let someone step up and maintain it in its own layer?
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2803) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1088)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is out for review.
*YP 5.0.10 is in QA.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 27th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 29th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 27th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 29th 10am GMT and Monday June 2nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in under review for release
*YP 5.2.1 is in QA
*YP 5.3 M1 is two weeks away
*Patches continue to merge into master for upgrades and fixes.
*Further pieces of the clang changes have merged.
*There is a potential pending change to wic to rename plugins, changing “-” to “_”, feedback welcome on if/how we should handle this as it could be invasive in impact.
*The clang build time and size increases continue to cause significant concern.
*fitimage changes from Adrian are nearly ready to merge once two issues have been resolved.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2803 (last week 2813) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1088 (last week 1096)
**Patches in the Pending State: 157 (14%) [last week 158 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is in QA.
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 20th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in QA
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*musl-qemuarm64 was also added to default testing
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*Many good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is in QA.
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 13th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 15th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 13th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 15th 10am GMT and Monday May 19th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 was released
*We’re happy to announce that RISC-V is becoming a officially supported architecture for Yocto Project: https://riscv.org/riscv-news/2025/05/risc-v-international-and-the-rise-project-join-forces-for-yocto-project-support/
**Thanks to all who helped make this happen!
*Patches merged to switch pseudo from a directory exclusion list to a directory inclusion list. This change has long been requested but is now working and merged.
*The clang merge caused significant build time increases (nearly double) as well as image size increases, all of which we need analysis to try and mitigate if possible.
*Qemu changes upstream mean running it on 32 bit hosts may soon not be possible. 64 bit emulation on 32 bit hosts has already been dropped.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Many other good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2791 (last week 2753) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1104 (last week 1075)
**Patches in the Pending State: 159 (14%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 was released.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 6th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 8th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 6th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 8th 10am GMT and Monday May 12th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 was released
*YP 5.2 rc2 is pending release and the rc1 issues were fixed
*The gcc 15 upgrade merged
*We merged the clang recipe into oe-core replacing llvm. There are further tweaks and improvements pending but this gives us a baseline to improve upon.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. Layers including meta-openembedded will need updating to avoid these accesses.
*Many other good upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2753 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1075 (last week 1071)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in review for release.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 was released.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 29th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 1st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 1st 10am GMT and Monday May 5th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 is pending release.
*YP 5.2 rc2 is in QA.
*We have fixes/workarounds merged for the most frequent recent autobuilder issues apart from the clang problem after the mesa merge and CDN issue (which is being worked on).
*Patches continue to merge into master as review/time/testing allows. We are seeing a high number of failures in incoming patches which take time to resolve.
*The gcc 15 upgrade is close to ready to merge but there are failures in layers outside core.
*The clang/llvm recipe merge patch series is now mostly passing autobuilder testing and would step us closer to the meta-clang merge. Review help appreciated.
*Various other upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2746) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1071 (last week 1068)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 rc2 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 is ready for release.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 22rd, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 22rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 24th 10am GMT and Monday Apr. 28th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*We plan to build YP 5.2 rc2 once fixes are merged for:
**Issues running glxgears (have a patch)
**Failure to boot on arrowlake platform (have a patch)
**genericarm64 has getty issues on some hardware platforms (no patch)
*YP 4.0.26 was released
*YP 5.0.9 is in QA
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*The mesa/llvm change has broken meta-clang causing autobuilder failures
*A recently merged wic test has intermittent failures
*Pending patches cause further breakage in various layers (e.g. qemu class change)
*Various other upgrades and fixes were merged to master

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2746 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1064)
**Patches in the Pending State: 140 (13%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 will have an rc2 built.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 was released.
*YP 5.0.9 is in QA.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 15th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 17th 10am GMT and Monday Apr. 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 rc1 has potential issues which may need an rc2:
**Issues running glxgears
**Failure to boot on arrowlake platform
**genericarm64 has getty issues on some hardware platforms
*YP 4.0.26 is out of QA and under review, likely to release
*Thanks to careful work, pending patches and overall total patches both decreased, thanks Alex.
*We upgraded mesa after some changes to the llvm build, thanks Dimitry.
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*We can now mark up python function variable dependencies using decorators, thanks Joshua.
*The bitbake whitespace change for assignment operators is ready to merge as we believe all autobuilder tested layers have updated.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1080)
**Patches in the Pending State: 144 (14%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 is in review.
*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.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.302 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 8th, 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:''' 
*Bug Triage meeting - Thursday Apr. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 10th 10am GMT and Monday Apr. 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.1.4 was released
*YP 5.2 rc1 is in QA
*YP 4.0.26 is ready for QA
*While 5.2 is in testing, master has continued to take patches which are ready.
*We are aiming to add more tag entries to SRC_URI for git SRCREV based recipes, please keep this in mind during upgrades.
*Some further analysis on the pseudo bug was posted
*There is a proposed whitespace syntax change with a pending bitbake patch to improve some consistency issues in formatting which can affect variable assignment.
*YP 5.3 Proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been separated from the clone servers so load spikes should only now impact the web interface.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2781) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1080)
**Patches in the Pending State: 167 (15%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.1.4 is released.
*YP 4.0.26 is ready for QA.
*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 

== Yocto Project Weekly Status Apr. 1st, 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:''' 
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1.4 is due for release
*Our first release candidate for YP 5.2 is ready for QA
*The walnascar branches have diverged from master
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 was released.
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.0.8 was released.
*YP 5.1.4 is ready for release.
*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 

== Yocto Project Weekly Status Mar. 25th, 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:''' 
*Bug Triage meeting - Thursday Mar. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 is due to be released
*YP 5.0.8 is due to be released
*YP 5.1.4 is in QA
*We are at feature freeze for YP 5.2 with our first rc build next week
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*SRC_URI entries for git now support tag verification against a specified source revision
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2801 (last week 2786) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1049)
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is ready for release.
*YP 5.1.4 is in QA.
*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 

== Yocto Project Weekly Status Mar. 18th, 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:''' 
*Bug Triage meeting Thursday Mar. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M3 has been through QA with one issue found
*YP 5.0.8 is in 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.
*Welcome improvements on syncing an sstate cache with a hash equivalence server were merged allowing more efficient hash equivalence server database cleanup, thanks!
*Bitbake python function library files were not always being cached correctly in bitbake’s parse cache, this was fixed.
*We started to merge gcc 15 fixes, particularly in native recipes as this will likely cause problems during the next release cycle with newer distro versions if we do not act.
*There were a number of minor version upgrades for bugs and CVE related issues.
*The recent annoying qemumips64 intermittent bug on the autobuilder looks to be a mips specific kernel issue which has been fixed upstream. We continue to wonder whether we should test mips/powerpc given the lack of interest in helping resolve issues.
*There are several fetcher changes pending including the ability to specify both a tag and a source revision.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2786 (last week 2816) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1049 (last week 1027)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is being reviewed.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is in 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 

== 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:''' 
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''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:''' 
*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.
*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.

'''Tracking Metrics:''' 
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*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:''' 
*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 

== Yocto Project Weekly Status Mar. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Mar. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 was released
*YP 5.1.3 is pending review
*We are now at feature freeze for YP 5.2
*Go was upgraded to 1.24, thanks to Jose and Hongxu for their work in making that happen and identifying the remaining reproducibility issue
*Rust upgrades to 1.83 and possibly 1.84 are close and we are aiming to include them in the release if possible
*The CVE/NVD situation is concerning enough we may delay the release build in the hope some improvements and process changes can be made.
*A cause of intermittent failures resulting in bitbake hangs was identified after 3 days of work from Richard (recursive events deadlocking)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*A new version of uninative compatible with glibc 2.41 was released.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2761) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1023)
**Patches in the Pending State: 170 (17%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 was released.
*YP 5.1.3 is in review.
*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 

== Yocto Project Weekly Status Feb. 25th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 is out of QA pending review
*YP 5.1.3 is in QA
*We are now 1 week from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*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/
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 is in review.
*YP 5.1.3 is in QA.
*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 

== Yocto Project Weekly Status Feb. 18th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.0.7 was released
*YP 4.0.25 is in QA
*We are now 2 weeks from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We plan to drop support for ifconfig now that the remaining usages in OE-Core have been patches to address them.
*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/ and in the weekly report last week. The situation remains unchanged.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2711 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1025)
**Patches in the Pending State: 172 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 was released.
*YP 4.0.25 is in QA.
*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 

== 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:''' 
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''Key Status/Updates:''' 
*YP 5.2 M2 was released
*YP 5.0.7 is under review and passed QA
*We are now 3 weeks from feature freeze for 5.2
*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’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**https://github.com/openembedded/openembedded-core/pulls
**https://github.com/openembedded/bitbake/pulls
*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.
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
*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/ :
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
***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:''' 
*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:''' 
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''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 

== Yocto Project Weekly Status Feb. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.24 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.0.7 was built and is ready for QA.
*We are now 4 weeks from feature freeze for 5.2
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*We plan to merge b4 configuration file support, thanks Quentin.
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Toolchain selection via virtual recipe specific providers was merged
*Patches for newer binutils, gdb and glibc are pending.
*The binutils upgrade removes gold linker support so that will be removed from core.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in review.
*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 4.0.24 was released.
*YP 5.0.7 is in QA.
*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 

== Yocto Project Weekly Status Jan. 28th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M2 was built and is in QA
*YP 5.0.7 was built and is ready for QA.
*YP 4.0.24 is in review.
*YP 5.1.2 was released
*Toolchain selection via virtual recipe specific providers was merged
*BB_CURRENT_MC behaviour was changed to default to an empty string rather than “default” to avoid complicating code to avoid bugs
*Bitbake-selftest was fixed to work with newly released git versions
*Problems were found with the gcc poison patches. Now they have been fixed, failures were found in some recipes showing host contamination issues
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2714 (last week 2724) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1024)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in QA.
*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 4.0.24 is ready for release.
*YP 5.1.2 was released.
*YP 5.0.7 is waiting for QA.
*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 

== Yocto Project Weekly Status Jan. 21st, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M1 was released, significantly delayed after several issues (see the release notes)
*YP 5.0.6 was released.
*YP 5.2 M2 is due to build this week, likely after the toolchain provider issues are resolved.
*YP 5.1.2 is under review for release
*YP 4.0.24 is still in QA
*After discussion and experimentation, support for toolchain selection via virtual/cross-cc is going to be added via a bitbake API, patches are under testing/review.
*Many good patches have been merged or are under review and close to merging, thanks all for the great work. Several do need small tweaks to get them over the line to the standard we need but it is great to see the variety and quality of the improvements.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2724 (last week 2763) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M1 was released.
*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 was released.
*YP 4.0.24 is in QA.
*YP 5.1.2 is ready for release.
*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 

== Yocto Project Weekly Status Jan. 14th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release 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)
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''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 175 (17%)]
*https://autobuilder.yocto.io/-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 is in QA.
*YP 5.1.2 is 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 

== Yocto Project Weekly Status Jan. 7th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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
**The issues are being investigated:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*YP 5.0.6 is ready to be released
*Feedback from Richard has now been given on the meta-clang merging patches which are not ready yet. Development work is needed to move this forward, a copy and paste into core isn’t enough and it will not merge without help from people.
*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.
*Patches using config fragment and include_all are being worked on in master-next for OE-Core.
*There is a proposed fix for some native class extension handling code bugs/issues however that fix creates new dependency problems and will require wider metadata changes.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2840 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1037 (last week 1046)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-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 in review.
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*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

Weekly Status

2025-12-16T15:51:18Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 9th, 2025 */

2025 Yocto Project Weekly Status Archive

2025-12-09T15:51:34Z

Stephen K. Jolley: /* Yocto Project Weekly Status Dec. 2nd, 2025 */

== Yocto Project Weekly Status Dec. 9th, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 11th 10am GMT and Monday Dec. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 was released
*YP 5.3 rc4 has passed QA and is under review
*The 5.3 QA report is available and no major release blocking issues were found so we should be able to finally make the release.
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*Welcome to Paul and Yoann in their new roles and huge thanks to Steve!
*Patches for master are merging and the builds are looking greener, there is a problem with the test result regression reports still causing failures as well as some check-layer issues.
*We have isolated the Fedora43 workers until we can root cause the binary problems it was causing when the sstate was shared to older systems
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*The project is exploring the idea of applying for funding for security related work. If anyone (individual or consultancies) has ideas, please talk to Paul/Richard/TSC. This is an opportunity to work on those issues you never have time/funding for!
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 6.0. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_6.0_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.
*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.

'''Tracking Metrics:''' 
*WDD 2978 (last week 2963) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1086 (last week 1080)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in review for release.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 was released.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 
== Yocto Project Weekly Status Dec. 2nd, 2025 ==
Current Dev Position: YP 5.3 M4 - Final Build QA and Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Dec. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Dec. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Dec. 4th 10am GMT and Monday Dec. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is due to be released
*YP 5.3 rc4 is built and due to enter QA
*There was an announcement about the new project roles: https://lists.openembedded.org/g/openembedded-architecture/message/2207
*There were a lot of problems encountered during the final 5.3 release build. Most of these should have been resolved.
*Patches started to merge for master development again. Unfortunately there is breakage on the autobuilder, probably from issues arising from Fedora 43 binaries being incompatible with older distros. Until this is resolved, patch flow will be limited.
*Further bitbake-setup changes under discussion for the new development cycle:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*We are considering entirely disabling the npm fetcher in bitbake due to the security issues until those are resolved.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2963 (last week 2953) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1082)
**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 in QA.

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 25th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 27th 10am GMT and Monday Dec. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.14 is under review for release.
*The final 5.3 build is still pending on fixing bugs from issues arising from the bitbake-setup changes. All other changes are now on hold for post release.
*We aim to build 5.3 when we have stable builds on the autobulder. Fixes from the changes around MACHINE/DISTRO conflict between conf/env and feature settings broke oe-selftest. The cooker feature change also exposed two existing bitbake *cache issues, particularly with memory resident bitbake. Those fixes merged but the fixes appear to be exposing further problems which are being investigated.
*Other potential changes that have been discussed but don’t have workable patches yet and are not going to block release::
**to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2953 (last week 2943) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1082 (last week 1066)
**Patches in the Pending State: 152 (14%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 5.0.14 is ready for release.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 18th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 20th 10am GMT and Monday Nov. 24th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*The final 5.3 build is still pending on resolving some rough edges on bitbake-setup. The patches so far have made a huge difference, thanks everyone who helped!
*We aim to build 5.3 when the remaining identified issues with bitbake-setup are resolved:
**Improvements to the default build directory path (json format string?)
**Handling potential MACHINE/DISTRO conflict between conf/env and feature settings
**Comments to toolcfg.conf about how to change
**Mention "bitbake-config-build enable-fragment machine/XXX" in bitbake-setup output
**Remove/change broken template files from meta-yocto
*Other potential changes that have been discussed but don’t have workable patches yet:
**defaulting to a common sstate directory and hashequiv server
**Allowing symlinking of local existing repos into the build instead of fetching
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2943 (last week 3048) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1066 (last week 1067)
**Patches in the Pending State: 175 (16%) [last week 175 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''YP 6.0 Milestone Dates:''' 
*YP 6.0 M1 Build Date 2026-01-05
*YP 6.0 M1 Release Date 2026-01-16
*YP 6.0 M2 Build Date 2026-02-02
*YP 6.0 M2 Release Date 2026-02-13
*YP 6.0 M3 Build Date 2026-03-02
*YP 6.0 M3 Release Date 2026-03-13
*YP 6.0 M4 Build Date 2026-03-30
*YP 6.0 M4 Release Date 2026-04-26

'''Upcoming dot releases:''' 
*YP 4.0.31 was released.
*YP 5.0.14 is in QA.
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16
*YP 5.3.1 Build Date 2026-01-12
*YP 5.3.1 Release Date 2026-01-23
*YP 4.0.33 Build Date 2026-01-26
*YP 4.0.33 Release Date 2026-01-30
*YP 5.0.16 Build Date 2026-02-09
*YP 5.0.16 Release Date 2026-02-20
*YP 5.3.2 Build Date 2026-02-16
*YP 5.3.2 Release Date 2026-02-27
*YP 4.0.34 Build Date 2026-02-23
*YP 4.0.34 Release Date 2026-03-06
*YP 5.3.3 Build Date 2026-03-09
*YP 5.3.3 Release Date 2026-03-20
*YP 5.0.17 Build Date 2026-03-16
*YP 5.0.17 Release Date 2026-03-23
*YP 4.0.35 Build Date 2026-04-06
*YP 4.0.35 Release Date 2026-04-17
*YP 5.3.4 Build Date 2026-04-13
*YP 5.3.4 Release Date 2026-04-24
*YP 5.0.18 Build Date 2026-04-20
*YP 5.0.18 Release Date 2026-05-01
*YP 5.0.19 Build Date 2026-05-26
*YP 5.0.19 Release Date 2026-06-05

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 11th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 11th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 13th 10am GMT and Monday Nov. 17th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 was released
*YP 4.0.31 is due to be released
*We are not yet ready to build 5.3 as there are too many rough edges on bitbake-setup: https://lists.openembedded.org/g/openembedded-architecture/message/2199
*The documentation changes related to bitbake-setup merged, thanks to all who have helped on these.
*We are now no longer updating the poky master branch. The distro in meta-yocto remains. Long live poky.
*Toaster is now working with bitbake-setup, huge thanks to David Reyna for resolving the issues there.
*Upstream linux kernel end-of-life’d 6.16 but we can’t get 6.17 working fully so we’ll be releasing with 6.16 and removing the 6.17 recipes (merged in error).
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns but we are lacking patches.
*We removed tcp-wrappers from OE-Core. It was late in but this should have happened long ago and if anyone is using it, you probably shouldn’t be!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3048 (last week 3103) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1067 (last week 1098)
**Patches in the Pending State: 175 (16%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 was released.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 4.0.31 is in review for release.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Nov. 4th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Nov. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Nov. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Nov. 6th 10am GMT and Monday Nov. 10th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 was released
*YP 5.3 M3 is due to be released
*YP 4.0.31 is in QA
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We plan to merge the documentation changes then stop updating the poky repository master branch.
*We are now past the feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. The 6.17 kernel has run into issues we don’t have availability/time to resolve unfortunately so we will have to release with 6.16.
*YP 6.0 (wrynose) and the next LTS releases proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3103 (last week 3001) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in review for release.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 was released.
*YP 4.0.31 is in QA.
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 28th, 2025 ==
Current Dev Position: YP 5.3 M4 - Stabilization and Final Build/Release 
Next Deadline: YP 5.3 M4 Build Date 2025-11-10 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 30th 10am GMT and Monday Nov. 3rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 is in QA
*YP 5.0.13 is under review for release
*Documentation updates related to many of the recent changes are in progress, thanks to all who have helped on these.
*We have now past feature freeze for YP 5.3. To be accepted, patches that have a high bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve these issues!
*Upstream linux kernel just end-of-life’d 6.16 but whinlatter contains 6.16. We are evaluating the situation with 6.17, feedback on it (for/against and known issues) would be welcome.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3001 (last week 3009) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 153 (14%) [last week 153 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-11-10
*YP 5.3 M4 Release Date 2025-11-28

'''Upcoming dot releases:''' 
*YP 5.0.13 is in review for release.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 21st, 2025 ==
Current Dev Position: YP 5.3 M4 
Next Deadline: YP 5.3 M4 Build Date 2025-10-06 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 23rd 10am GMT and Monday Oct. 27th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M3 and 5.0.13 currently in QA.
*YP 5.2.4 has been released
*We’re at feature freeze for YP 5.3. Patches that will be accepted now have a higher bar until after we branch master from whinlatter. Known issues:
**check-layer tests are now running under nodistro instead of poky, so some layers are failing as they assume some DISTRO_FEATURES are enabled.
**Toaster is broken with bitbake-setup (#16012). Help moving to supporting non-poky layouts would be good if anyone is using Toaster.
**The patch/cve metrics jobs need reviewing to be sure they’re correct with bitbake-setup (#16013)
**The build performance jobs don’t know that poky and oe-core are the same so the charts are currently wrong (#16014)
**Help welcomed to resolve this issues!
*Rust now reuses the same LLVM as Clang, and the rust-llvm recipe has been deleted. Many thanks to Deepesh and others at Wind River!. There’s a known regression building rust with clang which is being investigated.
*Upstream kernel just end-of-life’d 6.16 but whinlatter will ship with 6.16. It’s probably too late to upgrade to 6.17 for the release, we’ll have to see as to whether we upgrade post-release.
*“poky” as a combo-layer repository will soon no longer be needed or updated for master and whinlatter branches.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 3009 (last week 2904) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1096)
**Patches in the Pending State: 153 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 is in QA.
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 was released.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.0.31 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 14th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 16th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 14th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 16th 10am GMT and Monday Oct. 20th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.13 is in QA.
*YP 5.2.4 is due to be released.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. The status is:
**llvm/clang split patches have merged
**bitbake-setup has merged
**the autobuilder has switched to use bitbake-setup for master builds
**there are build issues with bitbake-setup that have shown up with check-layer targets
**fixes for the reproducibility problem in perf from 6.16 are being tested
*“poky” as a combo-layer repository will soon no longer be needed or updated.
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2904 (last week 2884) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.4 is ready for release.
*YP 5.0.13 is in QA.
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Oct. 7th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Oct. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 9th 10am GMT and Monday Oct. 13th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is under review.
*YP 5.3 M3 is due to build soon.
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (patches ready and in testing)
**Merging of bitbake-setup
*Bitbake-setup is nearing being ready for merging, there is one oe-selftest related issue we need to resolve first. Apart from this it is running successfully on the autobuilder.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*The proposal to allow backporting of SPDX 3 support to scarthgap was accepted by the TSC, assuming tests are added and pass.
*There is an open Yocto Project position which we’re in the process of advertising:
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2884 (last week 2854) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1103)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 was released.
*YP 5.2.4 is ready for release.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 30th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Oct. 2nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 30th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Oct. 2nd 10am GMT and Monday Oct. 6th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is under review for release
*YP 5.2.4 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still need to resolve before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang (currently blocked by uninative issues with llvm static libs)
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2854 (last week 2846) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1103 (last week 1105)
**Patches in the Pending State: 154 (14%) [last week 154 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is ready for release.
*YP 5.2.4 is in QA.
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 23rd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 25th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 23rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 25th 10am GMT and Monday Sept. 29th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.30 is in QA
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3. There are three pending items we still aim to merge before building:
**Fixing a reproducibility problem in perf from 6.16
**Split of llvm from clang
**Merging of bitbake-setup once the autobuilder can use it
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are likely going to be breaking changes to the npm fetcher related to ongoing security concerns.
*There is a proposal to the TSC requesting an exception to allow backporting of SPDX 3 support to scarthgap. Please comment on the list in support of or against this as appropriate, the TSC is leading towards granting the exception.
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2846 (last week 2828) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1105 (last week 1112)
**Patches in the Pending State: 154 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.30 is in QA.
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 16th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 18th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 16th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 18th 10am GMT and Monday Sept. 22nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*We have now updated to the 6.16 linux kernel
*There are clang/llvm performance improvements we plan to merge before building 5.3 (Thanks Ross!)
*We aim to merge bitbake-setup before building 5.3 M3, work is currently being done to migrate the autobuilder to use it.
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2828 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1112 (last week 1111)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 was released.
*YP 5.0.12 was released.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 9th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 11th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 9th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 11th 10am GMT and Monday Sept. 15th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2.3 is due to be released.
*YP 5.0.12 is due to be released.
*YP 5.3 M3 is due to build soon
*We’re at feature freeze for YP 5.3
*Updates to the 6.16 kernel are pending before the 5.3 M3 build
*We aim to merge bitbake-setup before building 5.3 M3
*This change will mean “poky” as a combo-layer repository will no longer be needed or updated. This means autobuilder changes before we build 5.3 M3.
*Patch merging is continuing as long as the risk for the changes are low
*There are a couple of open Yocto Project positions which we’re in the process of advertising:
**Ecosystem Engineering and Operations Lead
**LTS Maintainer - Steve Sakoman is retiring in April 2026 (full details pending)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1111 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is being reviewed for release.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Sept. 2nd, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Sept. 4th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Sept. 2nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Sept. 4th 10am GMT and Monday Sept. 8th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*RP is on holiday this week so should not be working
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA
*YP 5.3 M3 is due to build shortly (and is feature freeze)
*Linux 6.16 has been integrated but is currently not the default
*Patches continue to merge into master for upgrades and fixes until M3 is built
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*The Embedded Linux Conference was a success, with lots of Yocto-related talks being full to capacity. The OpenEmbedded and Yocto Project mini conferences were well attended and very interesting. Thanks to everyone who attended and made it a great event!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2845 (last week 2835) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1096)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.3 is being reviewed for release.
*YP 5.0.12 is in QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 26th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 28th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 26th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 28th 10am GMT and Monday Sept. 1st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 was released
*YP 5.2.3 is in QA
*YP 5.0.12 is waiting for QA
*YP 5.3 M3 is due to build in one week (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays and conferences.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*A 6.16 kernel recipe is available but we haven’t switched to it yet
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2835 (last week 2878) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1095)
**Patches in the Pending State: 156 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 was released.
*YP 5.2.3 is in QA.
*YP 5.0.12 is waiting for QA.
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 19th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 21st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 19th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 21st 10am GMT and Monday Aug. 25th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.29 is due to be released
*YP 5.2.3 is in QA
*YP 5.3 M3 is due to build in two weeks (and is feature freeze)
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Lttng component upgrades merged (babeltrace2 python enabling, lttng-modules, lttng-ust and lttng-tools) after several issues were resolved, particularly ptest failures.
*The kernel upgrade to 6.16 is under development. The libc-headers merged and is no longer blocked on lttng due to the upgrades above.
*A new version of bitbake-setup is in master-next and is making huge progress in readiness, thanks Alexander Kanavin!
*For M3, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2848 (last week 2838) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1095 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 155 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is ready release.
*YP 5.2.3 is in QA.
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 12th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 14th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 12th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 14th 10am GMT and Monday Aug. 18th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 was released
*YP 4.0.29 is in QA
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*Images are now .zst compressed by default
*Bitbake variable “filter” support merged, which is useful to make class extension internals (and hence parse time) more efficient.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Glibc was upgraded to 2.42 with a new uninative added for the new version
*The kernel upgrade to 6.16 is blocked on lttng-modules which doesn’t support the new kernel version yet.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2838 (last week 2841) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1098)
**Patches in the Pending State: 155 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 was released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 is in QA.
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Aug. 5th, 2025 ==
Current Dev Position: YP 5.3 M3 
Next Deadline: YP 5.3 M3 Build Date 2025-09-01 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Aug. 7th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Aug. 5th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Aug. 7th 10am GMT and Monday Aug. 11th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*xz is now a required host tool
*Patches are proposed to change the default images to be .zst compressed since these work better for releases and sharing
*Compressed images have implications for runqemu which needs to be run in snapshot mode to boot them
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. There is some minor improvement with recent patches but much work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2841 (last week 2826) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is to be released.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 29th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 31st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 31st 10am GMT and Monday Aug. 4th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 rc2 is in QA
*YP 5.0.11 was released
*Patches continue to merge into master for upgrades and fixes.
*Things have noticeably slowed due to holidays.
*The lldb reproducibility regression was resolved, thanks!
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress but nuch work remains to regain speed/space.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2826 (last week 2799) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1098 (last week 1096)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 is in QA.
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.11 was released.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 22nd, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 22nd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 24th 10am GMT and Monday July 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build this week.
*YP 5.2.2 was released
*YP 5.0.11 is due to be released
*Patches continue to merge into master for upgrades and fixes.
*We have a reproducibility regression in lldb which needs fixing urgently due to CI failures.
*We were able to root cause and resolve the 5.3 M1 QA reported gtk-play regression.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. We do have some mitigation patches in progress.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X merged, thanks to everyone who helped with fixes.
*Fixes for bitbake for python 3.14 around multiprocessing have been proposed. There are also bitbake profiling fixes for python 3.12+ and some small performance tweaks.
*For M3, the following changes have been mentioned as possibilities:
**Bitbake-setup (although this is feeling not ready and too late for the next LTS)
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2799 (last week 2824) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1099)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.2.2 was released.
*YP 5.0.11 is ready for release.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 15th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 17th 10am GMT and Monday July 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M2 is due to build next week however we still need to look into and fix the issue found in M1: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
*Help in debugging and fixing this would be very welcome.
*YP 5.2.2 is due to be released.
*YP 5.0.11 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time (41min -> 76min) and size (350MB -> 535MB) increases continue to cause significant concern. Patches from Ross start to split up the clang build and helped with a 5% speed improvement, thanks!
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*cmake 4.X is ready to merge for core. The fixes to meta-openembedded are much appreciated.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (final part)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2824 (last week 2800) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1099 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 156 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 was released.
*YP 5.2.2 is ready for release.
*YP 5.0.11 is in QA.
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 8th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 10th 10am GMT and Monday July 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 was released. We still need to look into and fix the issue found: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is due to be released.
*YP 5.2.2 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*There are problems with building native recipes with clang on the autobuilder which are suggesting deeper issues in our gcc files layout.
*A fix for a rare parsing hang has merged and some tweaks to the parsing queueing process are under discussion.
*cmake 4.X is ready to merge for code but is causing significant (~100 recipes) breakage in meta-openembedded. We will hold off a short while but this will merge soon. Khem needs help to fix the recipes there.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 3)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2800 (last week 2770) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1091)
**Patches in the Pending State: 156 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 was released.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is ready for release.
*YP 5.2.2 is in QA.
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status July 1st, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday July 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday July 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday July 3rd 10am GMT and Monday July 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is due to be released. One issue was found which needs to be fixed during M2: https://bugzilla.yoctoproject.org/show_bug.cgi?id=15915
**Help in debugging and fixing this would be very welcome.
*YP 4.0.28 is in QA.
*Patches continue to merge into master for upgrades and fixes.
*There were git tag improvements meaning we can now start adding these to SRC_URIs in all cases as shallow clone tarballs now account for them.
*The clang build time and size increases continue to cause significant concern.
*Patches to improve gomod support in devtool merged.
*The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*OE_SHARED_UMASK was added to control the umask used for files created in the shared DL_DIR and SSTATE_DIR directories.
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2770 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1091 (last week 1093)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 is ready for release.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 is in QA.
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 24th, 2025 ==
Current Dev Position: YP 5.3 M2 
Next Deadline: YP 5.3 M2 Build date 2025-07-21 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 26th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 24th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 26th 10am GMT and Monday June 30th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.3 M1 is in QA
*Patches continue to merge into master for upgrades and fixes.
*The UNPACKDIR layout changes merged. This has been disruptive for layers and it will take a while for changes to filter through various layers. It does set up better in the future with tools like devtool to avoid having lots of legacy layouts to support, and cleans up git recipes to be easier to write going forward.
*To support this, the layer series was updated to whinlatter in core.
*The clang build time and size increases continue to cause significant concern.
*There are patches in progress for improving gomod support in devtool and the mirroring issue for gomod was resolved.The main mirroring issues left are around “downloadfilename” support in urls which likely needs to be rewritten.
*Support for BUILDHISTORY_RESET was removed as it was error prone and better handled on the CI side of integration.
*OE-Core is adopting the use of glvnd for libGL abstraction
*The initial RISC-V tune changes merged
*Support for distro/machine selection with builtin fragments was added.
*A section was added to the manual on primary and secondary architecture/feature support for Yocto Project: https://docs.yoctoproject.org/dev/ref-manual/yocto-project-supported-features.html
*An email about this was sent to the openembedded-architecture list: https://lists.openembedded.org/g/openembedded-architecture/message/2162
*For M2, the following changes have been mentioned as possibilities:
**bitbake-setup
**wic split from OE-Core
**RISC-V tune changes (part 2)
**go/gomod fetcher changes
**switch classextend to use [filter] support from bitbake

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1093 (last week 1084)
**Patches in the Pending State: 157 (14%) [last week 158 (19%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 in QSA.
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 17th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 19th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 17th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 19th 10am GMT and Monday June 23rd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.10 was released
*YP 5.3 M1 is due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection patches have merged
*For M2, the following changes have been mentioned as possibilities:
**Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
**bitbake-setup
**bitbake config fragment support for distro/machine
**wic split from OE-Core
**RISC-V tune changes
**go/gomod fetcher changes

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2777 (last week 2740) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1084 (last week 1089)
**Patches in the Pending State: 158 (15%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.10 was released.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 10th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 12th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 10th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 12th 10am GMT and Monday June 16th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 were released.
*YP 5.0.10 is due to be released.
*YP 5.3 M1 is now due to build
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Patches for changing the workdir layout for unpack have been proposed with potentially significant impact for git based recipes. Feedback/review is welcome.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*Patches were sent out for a proposed toolchain selection mechanism implementation, feedback/review is welcome.
*Icecc.bbclass was removed.
*lz4 was removed from HOSTTOOLS as it was unneeded.
*Fitimage restructuring was merged, thanks Adrian.
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder so far, huge thanks to Michael Halstead for working on this.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2740 (last week 2778) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1089)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 was released.
*YP 5.2.1 was released.
*YP 5.0.10 is ready for release.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status June 3rd, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday June 5th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday June 3rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday June 5th 10am GMT and Monday June 9th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 and YP 5.2.1 are due to be released.
*YP 5.0.10 is in QA.
*YP 5.3 M1 is one weeks away
*Patches continue to merge into master for upgrades and fixes.
*The clang build time and size increases continue to cause significant concern.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.
*The toolchain selection mechanism is proving challenging as both the toolchain inherit and class extensions like native both need to happen ‘last’ and both involve overrides that are involved in deferred inherits. This issue may need bitbake changes to resolve.
*Should we drop icecc.bbclass and let someone step up and maintain it in its own layer?
*The project has switched to a different CDN setup with a different URL. This is proving reliable on the autobuilder 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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2778 (last week 2803) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1089 (last week 1088)
**Patches in the Pending State: 157 (14%) [last week 157 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is out for review.
*YP 5.0.10 is in QA.
*YP 4.0.28 Build Date 2025-06-30
*YP 4.0.28 Release Date 2025-07-11
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 27th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 29th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 27th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 29th 10am GMT and Monday June 2nd 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in under review for release
*YP 5.2.1 is in QA
*YP 5.3 M1 is two weeks away
*Patches continue to merge into master for upgrades and fixes.
*Further pieces of the clang changes have merged.
*There is a potential pending change to wic to rename plugins, changing “-” to “_”, feedback welcome on if/how we should handle this as it could be invasive in impact.
*The clang build time and size increases continue to cause significant concern.
*fitimage changes from Adrian are nearly ready to merge once two issues have been resolved.
*Changes to workdir layout for unpack are being considered with potentially significant impact for git based recipes requiring recipe changes.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2803 (last week 2813) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1088 (last week 1096)
**Patches in the Pending State: 157 (14%) [last week 158 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is out for review.
*YP 5.2.1 is in QA.
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 20th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 22nd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 20th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 22nd 10am GMT and Monday May 26th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 4.0.27 is in QA
*qemuriscv64, qemuriscv64-tc (toolchain) and qemuriscv64-ptest were added to default testing on the autobuilder
*musl-qemuarm64 was also added to default testing
*The clang build time and size increases continue to cause significant concern.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Due to many recent changes such as gcc and clang, patch counts have risen significantly. We now need to focus on finding ways to reduce the numbers of Pending and Inappropriate patches.
*Many good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2813 (last week 2791) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1096 (last week 1104)
**Patches in the Pending State: 158 (14%) [last week 159 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 is in QA.
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 13th, 2025 ==
Current Dev Position: YP 5.3 M1 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 15th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 13th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 15th 10am GMT and Monday May 19th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 was released
*We’re happy to announce that RISC-V is becoming a officially supported architecture for Yocto Project: https://riscv.org/riscv-news/2025/05/risc-v-international-and-the-rise-project-join-forces-for-yocto-project-support/
**Thanks to all who helped make this happen!
*Patches merged to switch pseudo from a directory exclusion list to a directory inclusion list. This change has long been requested but is now working and merged.
*The clang merge caused significant build time increases (nearly double) as well as image size increases, all of which we need analysis to try and mitigate if possible.
*Qemu changes upstream mean running it on 32 bit hosts may soon not be possible. 64 bit emulation on 32 bit hosts has already been dropped.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. We need to work out how to handle this for go recipes in particular in meta-openembedded
*Many other good upgrades and fixes were merged to master.

'''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://dashboard.yoctoproject.org/bugtriage/#newcomer-container
*There are bugs that are currently unassigned for YP 5.3. See: https://wiki.yoctoproject.org/wiki/Bug_Triage#Medium+_5.3_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.
*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.

'''Tracking Metrics:''' 
*WDD 2791 (last week 2753) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1104 (last week 1075)
**Patches in the Pending State: 159 (14%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 was released.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status May 6th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 8th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday May 6th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 8th 10am GMT and Monday May 12th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 was released
*YP 5.2 rc2 is pending release and the rc1 issues were fixed
*The gcc 15 upgrade merged
*We merged the clang recipe into oe-core replacing llvm. There are further tweaks and improvements pending but this gives us a baseline to improve upon.
*Network access outside of do_fetch now causes yocto-check-layer to fail which is a new change/requirement for Yocto Compatible v3. Layers including meta-openembedded will need updating to avoid these accesses.
*Many other good upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2753 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1075 (last week 1071)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in review for release.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 was released.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 29th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday May 1st at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 29th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday May 1st 10am GMT and Monday May 5th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.0.9 is pending release.
*YP 5.2 rc2 is in QA.
*We have fixes/workarounds merged for the most frequent recent autobuilder issues apart from the clang problem after the mesa merge and CDN issue (which is being worked on).
*Patches continue to merge into master as review/time/testing allows. We are seeing a high number of failures in incoming patches which take time to resolve.
*The gcc 15 upgrade is close to ready to merge but there are failures in layers outside core.
*The clang/llvm recipe merge patch series is now mostly passing autobuilder testing and would step us closer to the meta-clang merge. Review help appreciated.
*Various other upgrades and fixes were merged to master.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2746) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1071 (last week 1068)
**Patches in the Pending State: 140 (13%) [last week 140 (13%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 rc2 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 5.0.9 is ready for release.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 22rd, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 24th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 22rd at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 24th 10am GMT and Monday Apr. 28th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*We plan to build YP 5.2 rc2 once fixes are merged for:
**Issues running glxgears (have a patch)
**Failure to boot on arrowlake platform (have a patch)
**genericarm64 has getty issues on some hardware platforms (no patch)
*YP 4.0.26 was released
*YP 5.0.9 is in QA
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*The mesa/llvm change has broken meta-clang causing autobuilder failures
*A recently merged wic test has intermittent failures
*Pending patches cause further breakage in various layers (e.g. qemu class change)
*Various other upgrades and fixes were merged to master

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2746 (last week 2756) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1064)
**Patches in the Pending State: 140 (13%) [last week 144 (14%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 will have an rc2 built.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 was released.
*YP 5.0.9 is in QA.
*YP 4.0.27 Build Date 2025-05-19
*YP 4.0.27 Release Date 2025-05-30
*YP 5.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.32 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 15th, 2025 ==
Current Dev Position: YP 5.2 Release Candidate Testing 
Next Deadline: YP 5.3 M1 Build date 2025-06-09 

'''Next Team Meetings:''' 
*Bug Triage meeting - Thursday Apr. 17th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 15th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 17th 10am GMT and Monday Apr. 21st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 rc1 has potential issues which may need an rc2:
**Issues running glxgears
**Failure to boot on arrowlake platform
**genericarm64 has getty issues on some hardware platforms
*YP 4.0.26 is out of QA and under review, likely to release
*Thanks to careful work, pending patches and overall total patches both decreased, thanks Alex.
*We upgraded mesa after some changes to the llvm build, thanks Dimitry.
*We are seeing initramfs size issues on genericarm64 on the autobuilder.
*We can now mark up python function variable dependencies using decorators, thanks Joshua.
*The bitbake whitespace change for assignment operators is ready to merge as we believe all autobuilder tested layers have updated.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2756 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1064 (last week 1080)
**Patches in the Pending State: 144 (14%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''YP 5.3 Milestone Dates:''' 
*YP 5.3 M1 Build Date 2025-06-09
*YP 5.3 M1 Release Date 2025-06-20
*YP 5.3 M2 Build Date 2025-07-21
*YP 5.3 M2 Release Date 2025-08-01
*YP 5.3 M3 Build Date 2025-09-01
*YP 5.3 M3 Release Date 2025-09-12
*YP 5.3 M4 Build Date 2025-10-06
*YP 5.3 M4 Release Date 2025-10-31

'''Upcoming dot releases:''' 
*YP 4.0.26 is in review.
*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.2.1 Build Date 2025-05-26
*YP 5.2.1 Build Date 2025-06-06
*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
*YP 5.2.2 Build Date 2025-07-07
*YP 5.2.2 Release Date 2025-07-18
*YP 5.0.11 Build Date 2025-07-14
*YP 5.0.11 Release Date 2025-07-25
*YP 4.0.29 Build Date 2025-08-11
*YP 4.0.29 Release Date 2025-08-25
*YP 5.2.3 Build Date 2025-08-18
*YP 5.2.3 Release Date 2025-08-29
*YP 5.0.12 Build Date 2025-08-25
*YP 5.0.12 Release Date 2025-09-05
*YP 4.0.30 Build Date 2025-09-22
*YP 4.0.30 Release Date 2025-10-03
*YP 5.2.4 Build Date 2025-09-29
*YP 5.2.4 Release Date 2025-10-10
*YP 5.0.13 Build Date 2025-10-13
*YP 5.0.13 Release Date 2025-10-24
*YP 4.0.31 Build Date 2025-11-03
*YP 4.031 Release Date 2025-11-14
*YP 5.0.14 Build Date 2025-11-17
*YP 5.0.14 Release Date 2025-11-28
*YP 4.0.32 Build Date 2025-12-15
*YP 4.0.302 Release Date 2025-12-24
*YP 5.0.15 Build Date 2026-01-05
*YP 5.0.15 Release Date 2026-01-16

'''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:''' 
https://wiki.yoctoproject.org/wiki/TSC 

== Yocto Project Weekly Status Apr. 8th, 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:''' 
*Bug Triage meeting - Thursday Apr. 10th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 8th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 10th 10am GMT and Monday Apr. 14th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.1.4 was released
*YP 5.2 rc1 is in QA
*YP 4.0.26 is ready for QA
*While 5.2 is in testing, master has continued to take patches which are ready.
*We are aiming to add more tag entries to SRC_URI for git SRCREV based recipes, please keep this in mind during upgrades.
*Some further analysis on the pseudo bug was posted
*There is a proposed whitespace syntax change with a pending bitbake patch to improve some consistency issues in formatting which can affect variable assignment.
*YP 5.3 Proposed timeline: https://docs.google.com/document/d/1BlvtPxpYsxHkeL10DFBQzBI9q_1HIk9r2FPxlfsQ95U/edit?tab=t.0
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been separated from the clone servers so load spikes should only now impact the web interface.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2781) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1080)
**Patches in the Pending State: 167 (15%) [last week 167 (15%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.1.4 is released.
*YP 4.0.26 is ready for QA.
*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 

== Yocto Project Weekly Status Apr. 1st, 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:''' 
*Bug Triage meeting - Thursday Apr. 3rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Apr. 1st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Apr. 3rd 10am GMT and Monday Apr. 7th 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 and YP 5.0.8 were released
*YP 5.1.4 is due for release
*Our first release candidate for YP 5.2 is ready for QA
*The walnascar branches have diverged from master
*qemumips, qemumips64 and qemuppc have been dropped from automated testing for walnascar and master onwards. Older releases will continue to have the testing they were released with.
*Some other autobuilder test targets were also tweaked to match current needs (e.g. fewer oe-selftest runs).
*Some disk usage improvements for rust were merged or queued for merge to help with overall build performance.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against. The cgit interface has been temporarily disabled at times of high load to help ensure clones work.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2781 (last week 2801) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1080 (last week 1060)
**Patches in the Pending State: 167 (15%) [last week 168 (16%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 was released.
*YP 5.2 M4 is in QA.

'''Upcoming dot releases:''' 
*YP 5.0.8 was released.
*YP 5.1.4 is ready for release.
*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 

== Yocto Project Weekly Status Mar. 25th, 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:''' 
*Bug Triage meeting - Thursday Mar. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync - Tuesday Mar. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Yocto Project Patch Review - Thursday Mar. Mar 27th 10am GMT and Monday Mar. 31st 9am PDT (https://zoom.us/j/97762397148?pwd=1xkiC9hp9SjEonaTaONwTb6iWry4Eb.1)

'''Project data dashboard: https://dashboard.yoctoproject.org/''' 

'''Key Status/Updates:''' 
*YP 5.2 M3 is due to be released
*YP 5.0.8 is due to be released
*YP 5.1.4 is in QA
*We are at feature freeze for YP 5.2 with our first rc build next week
*We have continued to merge gcc 15 fixes in anticipation of being prepared for host distro changes in the next six months.
*The minimum python version was increased to 3.9 with support for Ubuntu 20.04 now requiring buildtools due to changing g++ requirements.
*SRC_URI entries for git now support tag verification against a specified source revision
*Bitbake fetcher support for multiple revisions in a single git SRC_URI entry was removed for code simplification.
*Kernel stable updates merged including a key qemumips fix and various CVE fixes.
*A pseudo bug was identified and there is a reproduction patch posted however we’re struggling to work out how to fix it. We do have a workaround for the underlying pciutils trigger.
*We are aware of 500/502 errors from the project git servers. These are caused by load from the significant number of AI crawlers the infrastructure is being overloaded with which is hard to mitigate against.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2801 (last week 2786) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1060 (last week 1049)
**Patches in the Pending State: 168 (16%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is ready for release.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is ready for release.
*YP 5.1.4 is in QA.
*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 

== Yocto Project Weekly Status Mar. 18th, 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:''' 
*Bug Triage meeting Thursday Mar. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M3 has been through QA with one issue found
*YP 5.0.8 is in 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.
*Welcome improvements on syncing an sstate cache with a hash equivalence server were merged allowing more efficient hash equivalence server database cleanup, thanks!
*Bitbake python function library files were not always being cached correctly in bitbake’s parse cache, this was fixed.
*We started to merge gcc 15 fixes, particularly in native recipes as this will likely cause problems during the next release cycle with newer distro versions if we do not act.
*There were a number of minor version upgrades for bugs and CVE related issues.
*The recent annoying qemumips64 intermittent bug on the autobuilder looks to be a mips specific kernel issue which has been fixed upstream. We continue to wonder whether we should test mips/powerpc given the lack of interest in helping resolve issues.
*There are several fetcher changes pending including the ability to specify both a tag and a source revision.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2786 (last week 2816) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1049 (last week 1027)
**Patches in the Pending State: 171 (17%) [last week 170 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M3 is being reviewed.
*YP 5.2 M4 Build Date 2025-03-31
*YP 5.2 M4 Release Date 2025-04-25

'''Upcoming dot releases:''' 
*YP 5.0.8 is in 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 

== 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:''' 
*Bug Triage meeting Thursday Mar. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''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:''' 
*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.
*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.

'''Tracking Metrics:''' 
*WDD 2816 (last week 2771) (https://wiki.yoctoproject.org/charts/combo.html)
*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:''' 
*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 

== Yocto Project Weekly Status Mar. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Mar. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Mar. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 was released
*YP 5.1.3 is pending review
*We are now at feature freeze for YP 5.2
*Go was upgraded to 1.24, thanks to Jose and Hongxu for their work in making that happen and identifying the remaining reproducibility issue
*Rust upgrades to 1.83 and possibly 1.84 are close and we are aiming to include them in the release if possible
*The CVE/NVD situation is concerning enough we may delay the release build in the hope some improvements and process changes can be made.
*A cause of intermittent failures resulting in bitbake hangs was identified after 3 days of work from Richard (recursive events deadlocking)
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*A new version of uninative compatible with glibc 2.41 was released.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2771 (last week 2761) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1023)
**Patches in the Pending State: 170 (17%) [last week 171 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 was released.
*YP 5.1.3 is in review.
*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 

== Yocto Project Weekly Status Feb. 25th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 - Feature Freeze 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 27th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 25th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.25 is out of QA pending review
*YP 5.1.3 is in QA
*We are now 1 week from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We are struggling to get stable releases to build cleanly due to intermittent failures, which places strain on everyone. Sadly, traction on help for the intermittent issues remains problematic.
*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/
*Bitbake-setup patches have been submitted but merging remains unlikely simply due to lack of participation in the review/testing process.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder. There would be ways to add short term fixes. The better fixes likely involve rewriting mirror url handling, which can’t be rushed into and discussions on that are stalling anyway.
*The newcomer bug list has been triaged and has a number of new issues added.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2761 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1023 (last week 1030)
**Patches in the Pending State: 171 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 4.0.25 is in review.
*YP 5.1.3 is in QA.
*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 

== Yocto Project Weekly Status Feb. 18th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 20th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 18th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.0.7 was released
*YP 4.0.25 is in QA
*We are now 2 weeks from feature freeze for 5.2
*Patch review remains a challenge due to the limited number of people involved and the volume and breadth of changes. That work distracts from work on areas like clang or other improvements.
*We plan to drop support for ifconfig now that the remaining usages in OE-Core have been patches to address them.
*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/ and in the weekly report last week. The situation remains unchanged.
*The gomod mirror issue in meta-openembedded continues to give failed builds on the autobuilder.

'''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.
*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.

'''Tracking Metrics:''' 
*WDD 2711 (last week 2711) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1025)
**Patches in the Pending State: 172 (17%) [last week 172 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*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 was released.
*YP 4.0.25 is in QA.
*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 

== 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:''' 
*Bug Triage meeting Thursday Feb. 13th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*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

'''Key Status/Updates:''' 
*YP 5.2 M2 was released
*YP 5.0.7 is under review and passed QA
*We are now 3 weeks from feature freeze for 5.2
*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’d like to request help to process the open github pull requests for openembedded-core and bitbake:
**https://github.com/openembedded/openembedded-core/pulls
**https://github.com/openembedded/bitbake/pulls
*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.
*The project has agreed guidance on AI submissions: https://lists.yoctoproject.org/g/docs/message/6300
*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/ :
**An occasional hang for non-kvm x86/x86-64 qemu images early in boot, see in multiple kernels including the recent 6.12:
***https://autobuilder.yoctoproject.org/valkyrie/#/builders/28/builds/955
***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:''' 
*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:''' 
*WDD 2711 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1025 (last week 1029)
**Patches in the Pending State: 172 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''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 

== Yocto Project Weekly Status Feb. 4th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Feb. 6th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Feb. 4th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 4.0.24 was released
*YP 5.2 M2 has completed QA and is under review.
*YP 5.0.7 was built and is ready for QA.
*We are now 4 weeks from feature freeze for 5.2
*Patch flow has continued normally, many good fixes, some upgrades and kernel stable updates were merged.
*Issues were identified in gomod mirror handling which means the autobuilder meta-oe mirroring target now continually fails. We need to find a solution to this issue ASAP. The alternative is we drop meta-oe mirroring.
*We plan to merge b4 configuration file support, thanks Quentin.
*Due to issues with newer glibc and issues with the valgrind upgrade, we will drop valgrind ptest support since nobody can maintain it.
*Toolchain selection via virtual recipe specific providers was merged
*Patches for newer binutils, gdb and glibc are pending.
*The binutils upgrade removes gold linker support so that will be removed from core.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2704 (last week 2714) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1029 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in review.
*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 4.0.24 was released.
*YP 5.0.7 is in QA.
*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 

== Yocto Project Weekly Status Jan. 28th, 2025 ==
Current Dev Position: YP 5.2 M3 
Next Deadline: YP 5.2 M3 Build date 2025-03-03 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 30th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 28th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M2 was built and is in QA
*YP 5.0.7 was built and is ready for QA.
*YP 4.0.24 is in review.
*YP 5.1.2 was released
*Toolchain selection via virtual recipe specific providers was merged
*BB_CURRENT_MC behaviour was changed to default to an empty string rather than “default” to avoid complicating code to avoid bugs
*Bitbake-selftest was fixed to work with newly released git versions
*Problems were found with the gcc poison patches. Now they have been fixed, failures were found in some recipes showing host contamination issues
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2714 (last week 2724) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1030 (last week 1024)
**Patches in the Pending State: 173 (17%) [last week 173 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M2 is in QA.
*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 4.0.24 is ready for release.
*YP 5.1.2 was released.
*YP 5.0.7 is waiting for QA.
*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 

== Yocto Project Weekly Status Jan. 21st, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 23rd at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 21st at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*Twitch - See https://www.twitch.tv/theyoctojester

'''Key Status/Updates:''' 
*YP 5.2 M1 was released, significantly delayed after several issues (see the release notes)
*YP 5.0.6 was released.
*YP 5.2 M2 is due to build this week, likely after the toolchain provider issues are resolved.
*YP 5.1.2 is under review for release
*YP 4.0.24 is still in QA
*After discussion and experimentation, support for toolchain selection via virtual/cross-cc is going to be added via a bitbake API, patches are under testing/review.
*Many good patches have been merged or are under review and close to merging, thanks all for the great work. Several do need small tweaks to get them over the line to the standard we need but it is great to see the variety and quality of the improvements.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2724 (last week 2763) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1024 (last week 1030)
**Patches in the Pending State: 173 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-release/patchmetrics/

'''YP 5.2 Milestone Dates:''' 
*YP 5.2 M1 was released.
*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 was released.
*YP 4.0.24 is in QA.
*YP 5.1.2 is ready for release.
*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 

== Yocto Project Weekly Status Jan. 14th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release 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)
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''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 175 (17%)]
*https://autobuilder.yocto.io/-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 is in QA.
*YP 5.1.2 is 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 

== Yocto Project Weekly Status Jan. 7th, 2025 ==
Current Dev Position: YP 5.2 M2 
Next Deadline: YP 5.2 M2 Release date 2025-01-20 

'''Next Team Meetings:''' 
*Bug Triage meeting Thursday Jan. 9th at 7:30 am PST (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
*Weekly Project Engineering Sync Tuesday Jan. 7th at 8 am PST (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
*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
**The issues are being investigated:
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15703
**https://bugzilla.yoctoproject.org/show_bug.cgi?id=15704
*YP 5.0.6 is ready to be released
*Feedback from Richard has now been given on the meta-clang merging patches which are not ready yet. Development work is needed to move this forward, a copy and paste into core isn’t enough and it will not merge without help from people.
*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.
*Patches using config fragment and include_all are being worked on in master-next for OE-Core.
*There is a proposed fix for some native class extension handling code bugs/issues however that fix creates new dependency problems and will require wider metadata changes.
*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
*We have a growing number of bugs in bugzilla, any help with them is appreciated.

'''Tracking Metrics:''' 
*WDD 2840 (last week 2845) (https://wiki.yoctoproject.org/charts/combo.html)
*OE-Core/Poky Patch Metrics
**Total patches found: 1037 (last week 1046)
**Patches in the Pending State: 174 (17%) [last week 175 (17%)]
*https://autobuilder.yocto.io/-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 in review.
*YP 4.0.24 Build Date 2025-01-06
*YP 4.0.24 Release Date 2025-01-17
*YP 5.1.2 Build Date 2025-01-13
*YP 5.1.2 Release Date 2025-01-24
*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