Weekly Status - Revision history

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

2026-03-31T14:48:32Z

Yocto Project Status 24 March 2026

← Older revision		Revision as of 14:48, 31 March 2026
Line 1:		Line 1:
	== Yocto Project Status 24 March 2026 ==		== Yocto Project Status 31 March 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~26th Mar~~. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday Apr. 2nd 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)		*Weekly Project Engineering Sync - Tuesday 31st 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 6.0 M2 has been released.		*YP 4.0.34 was released.
	*YP 4.0.34 ~~is due to be~~ released.		*YP 5.3.3 is approved for release.
	*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 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.		*YP 6.0 M3 is now due to build however there are still key changes missing.
	**Issues still pending:		*Issues still pending:
	**Splitting wic into an external tool.		**Splitting wic into an external tool.
	**~~Deprecation of ltp (upstream dropped runltp and mandate kirk)~~		**Converting scripts/run-cvecheck to sbom-cve-check
			**DISTRO_FEATURES defaults improvements.
			**RHEL 9 xattrs/selinux/tar issue
	**How to improve DEBUG_BUILD?		**How to improve DEBUG_BUILD?
	**~~DISTRO_FEATURES defaults improvements~~.		**RHEL 10/openSUSE Leap 16.0/Ubuntu 26.04 support
	**SBOM/~~cve-check changes~~.
	**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
	*Issues that are mostly known quantities still needing work:		*Issues that are mostly known quantities still needing work:
	**x86 kvm seemingly broken with certain CPU features (#16074)		**x86 kvm seemingly broken with certain CPU features (#16074)
	**Failure to generate regression reports in release builds		**Failure to generate regression reports in release builds
	**Reconcile poky and OE-Core defaults templates.		**Fixing yocto-check-layer to work with --machines (many fixes merged)
	**Resolve Fedora 43 selftest failures
	**Fixing yocto-check-layer to work with ~~–machines~~
	*Issues that were resolved this week:		*Issues that were resolved this week:
	**~~Switching to pkg~~-~~config.~~		**Sbom-cve-check added
	**~~Allowing non-destructive git fetcher updates for~~ bitbake-setup ~~(further tweaks still being discussed)~~		**Replacement of runtlp with kirk (Thanks Daniel!)
	*We ~~are seeing issues with older versions of tar on RHEL 9 derived distros (selinux triggers due~~ to ~~xattrs)~~		**bitbake-setup vscode integration
	*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.		**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:'''<br/>		'''Ways to contribute:'''<br/>
Line 45:		Line 46:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2841~~ (last week ~~2866~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2814 (last week 2819) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1069~~ (last week ~~1081~~)		**Total patches found: 1062 (last week 1072)
	**Patches in the Pending State: ~~152~~ (14%) [last week 151 (14%)]		**Patches in the Pending State: 148 (14%) [last week 151 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M2 was released.
	*YP 6.0 M3 Build Date 2026-03-23		*YP 6.0 M3 Build Date 2026-03-23
	*YP 6.0 M3 Release Date 2026-04-08		*YP 6.0 M3 Release Date 2026-04-08
Line 59:		Line 59:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 4.0.34 ~~ready for release~~.		*YP 4.0.34 was released.
	*YP 5.3.3 ~~is in review~~.		*YP 5.3.3 ready for release.
	*YP 5.0.17 Build Date 2026-03-30		*YP 5.0.17 Build Date 2026-03-30
	*YP 5.0.17 Release Date 2026-04-15		*YP 5.0.17 Release Date 2026-04-15

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

2026-03-24T14:43:05Z

Yocto Project Status 17 March 2026

← Older revision		Revision as of 14:43, 24 March 2026
Line 1:		Line 1:
	== Yocto Project Status 17 March 2026 ==		== Yocto Project Status 24 March 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~19th~~ Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 26th 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)		*Weekly Project Engineering Sync - Tuesday 24th 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 5.~~3.2~~ has been released		*YP 6.0 M2 has been released.
	*YP 6.0 M2 is due to be released		*YP 4.0.34 is due to be released.
	*YP 4.0.34 is in QA.		*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 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.		*YP 6.0 M3 is now due to build however there are many key changes needed still missing.
	*~~We have issues we need to resolve before M3:~~		**Issues still pending:
	**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.		**Splitting wic into an external tool.
	**Switching to pkg-config.
	**Deprecation of ltp (upstream dropped runltp and mandate kirk)		**Deprecation of ltp (upstream dropped runltp and mandate kirk)
	**How to improve DEBUG_BUILD?		**How to improve DEBUG_BUILD?
	**DISTRO_FEATURES defaults improvements.		**DISTRO_FEATURES defaults improvements.
	**SBOM/cve-check changes.		**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.		**Reconcile poky and OE-Core defaults templates.
	**Resolve Fedora 43 selftest failures		**Resolve Fedora 43 selftest failures
	*~~glibc was upgraded 2~~.~~43 and we released a new uninative to match~~		**Fixing yocto-check-layer to work with –machines
	*~~runqemu now has better handling~~ for ~~different display outputs including VNC on unix domain sockets~~		*Issues that were resolved this week:
	*We are ~~adding testing~~ of ~~ptests~~ on ~~musl~~ to ~~our test matrix~~		**Switching to pkg-config.
	*Kernel rust support has merged		**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.		*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:'''<br/>		'''Ways to contribute:'''<br/>
Line 54:		Line 52:

	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M2 ~~is ready for release~~.		*YP 6.0 M2 was released.
	*YP 6.0 M3 Build Date 2026-03-23		*YP 6.0 M3 Build Date 2026-03-23
	*YP 6.0 M3 Release Date 2026-04-08		*YP 6.0 M3 Release Date 2026-04-08
Line 61:		Line 59:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.2 is released.		*YP 4.0.34 ready for release.
	*YP 4.0.34 ~~is in QA~~.		*YP 5.3.3 is in review.
	*YP 5.3.3 is in QA.
	*YP 5.0.17 Build Date 2026-03-30		*YP 5.0.17 Build Date 2026-03-30
	*YP 5.0.17 Release Date 2026-04-15		*YP 5.0.17 Release Date 2026-04-15

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

2026-03-17T14:51:44Z

Yocto Project Status 10 March 2026

← Older revision		Revision as of 14:51, 17 March 2026
Line 1:		Line 1:
	== Yocto Project Status 10 March 2026 ==		== Yocto Project Status 17 March 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~12th~~ Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 19th 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)		*Weekly Project Engineering Sync - Tuesday 17th 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 5.0.16 has been released		*YP 5.3.2 has been released
	*YP 5.~~3.2~~ is due to be released		*YP 6.0 M2 is due to be released
	*YP 6.0 M2 is in QA
	*YP 4.0.34 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 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.		*YP 6.0 M3 is due to build next week however there are many key changes needed still missing.
	*We have issues ~~which~~ need ~~further work that will block~~ M3:		*We have issues we need to resolve before M3:
	**x86 kvm seemingly broken with certain CPU features (#16074)		**x86 kvm seemingly broken with certain CPU features (#16074)
	**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)		**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
	**Failure to generate regression reports in release builds		**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.		**Allowing non-destructive git fetcher updates for bitbake-setup.
	**Splitting wic into an external tool.		**Splitting wic into an external tool.
	**Kernel rust support.
	**Switching to pkg-config.		**Switching to pkg-config.
	**Deprecation of ltp (upstream dropped runltp and mandate kirk)		**Deprecation of ltp (upstream dropped runltp and mandate kirk)
Line 31:		Line 28:
	**SBOM/cve-check changes.		**SBOM/cve-check changes.
	**Reconcile poky and OE-Core defaults templates.		**Reconcile poky and OE-Core defaults templates.
	**~~Switch to internal VNC server in QEMU~~		**Resolve Fedora 43 selftest failures
	**update to glibc 2.43 so we ~~can release~~ a new uninative		*glibc was upgraded 2.43 and we released a new uninative to match
	*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.~~		*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.		*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		*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~~!		*Thanks to everyone who helped out with the booth at Embedded World, it was a great success!

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 48:		Line 47:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2866~~ (last week ~~2908~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2841 (last week 2866) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1081~~ (last week ~~1103~~)		**Total patches found: 1069 (last week 1081)
	**Patches in the Pending State: ~~151~~ (14%) [last week 151 (14%)]		**Patches in the Pending State: 152 (14%) [last week 151 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M2 is ~~in QA~~.		*YP 6.0 M2 is ready for release.
	*YP 6.0 M3 Build Date 2026-03-23		*YP 6.0 M3 Build Date 2026-03-23
	*YP 6.0 M3 Release Date 2026-04-08		*YP 6.0 M3 Release Date 2026-04-08
Line 62:		Line 61:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.16 is released.		*YP 5.3.2 is released.
	*YP 5.3.2 is released.
	*YP 4.0.34 is in QA.		*YP 4.0.34 is in QA.
	*YP 5.3.3 ~~Build Date 2026-03-16~~		*YP 5.3.3 is in QA.
	*YP 5.~~3.3 Release Date 2026-04-01~~
	*YP 5.0.17 Build Date 2026-03-30		*YP 5.0.17 Build Date 2026-03-30
	*YP 5.0.17 Release Date 2026-04-15		*YP 5.0.17 Release Date 2026-04-15

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

2026-03-10T14:56:17Z

Yocto Project Status 3 March 2026

← Older revision		Revision as of 14:56, 10 March 2026
Line 1:		Line 1:
	== Yocto Project Status 3 March 2026 ==		== Yocto Project Status 10 March 2026 ==
	Current Dev Position: YP 6.0 M3<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M3 Build Date 2026-03-09<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-23<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~5th~~ Mar. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 12th 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)		*Weekly Project Engineering Sync - Tuesday 10th 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.33 has been released		*YP 5.0.16 has been released
	*YP 5.0.16 is ~~in TSC review~~		*YP 5.3.2 is due to be released
	*YP 6.0 M2~~, 5.3.2, &~~ 4.0.34 ~~are~~ in QA.		*YP 6.0 M2 is in QA
	**We are ~~aware of~~ changes ~~in QA timelines and are discussing how to address them~~.		*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:		*We have issues which need further work that will block M3:
	**x86 kvm seemingly broken with certain CPU features (#16074)		**x86 kvm seemingly broken with certain CPU features (#16074)
	**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)		**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
	**Failure to generate regression reports in release builds		**Failure to generate regression reports in release builds
	*We also have issues we need to resolve before ~~release~~:		*We also have issues we need to resolve before M3:
	**Allowing non-destructive git fetcher updates for bitbake-setup.		**Allowing non-destructive git fetcher updates for bitbake-setup.
	**Splitting wic into an external tool.		**Splitting wic into an external tool.
Line 29:		Line 31:
	**SBOM/cve-check changes.		**SBOM/cve-check changes.
	**Reconcile poky and OE-Core defaults templates.		**Reconcile poky and OE-Core defaults templates.
	*OE-~~Core switched~~ to ~~enabling a hash equivalence server by default~~.		**Switch to internal VNC server in QEMU
	*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.		**update to glibc 2.43 so we can release a new uninative
	*The project has a booth at Embedded World ~~next~~ week, feel free to come and say Hi if you’re there!		*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:'''<br/>		'''Ways to contribute:'''<br/>
Line 43:		Line 48:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2908~~ (last week ~~2893~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2866 (last week 2908) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~11063~~ (last week ~~1107~~)		**Total patches found: 1081 (last week 1103)
	**Patches in the Pending State: 151 (14%) [last week 151 (14%)]		**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
Line 51:		Line 56:
	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M2 is in QA.		*YP 6.0 M2 is in QA.
	*YP 6.0 M3 Build Date 2026-03-09		*YP 6.0 M3 Build Date 2026-03-23
	*YP 6.0 M3 Release Date 2026-03-20		*YP 6.0 M3 Release Date 2026-04-08
	*YP 6.0 M4 Build Date 2026-03-30		*YP 6.0 M4 Build Date 2026-04-13
	*YP 6.0 M4 Release Date 2026-04~~-26~~		*YP 6.0 M4 Release Date 2026-05-04

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.16 is ~~in review~~.		*YP 5.0.16 is released.
	*YP 5.3.2 is ~~in QA~~.		*YP 5.3.2 is released.
	*YP 4.0.34 is in QA.		*YP 4.0.34 is in QA.
	*YP 5.3.3 Build Date 2026-03-09		*YP 5.3.3 Build Date 2026-03-16
	*YP 5.3.3 Release Date 2026-03-20		*YP 5.3.3 Release Date 2026-04-01
	*YP 5.0.17 Build Date 2026-03-16		*YP 5.0.17 Build Date 2026-03-30
	*YP 5.0.17 Release Date 2026-03-23		*YP 5.0.17 Release Date 2026-04-15
	*YP 4.0.35 Build Date 2026-04-06		*YP 4.0.35 Build Date 2026-04-06
	*YP 4.0.35 Release Date 2026-04-17		*YP 4.0.35 Release Date 2026-04-22
	*YP 5.3.4 Build Date 2026-04-13		*YP 5.3.4 Build Date 2026-04-20
	*YP 5.3.4 Release Date 2026-04-24		*YP 5.3.4 Release Date 2026-05-06
	*YP 5.0.18 Build Date 2026-04-20		*YP 5.0.18 Build Date 2026-04-27
	*YP 5.0.18 Release Date 2026-05-01		*YP 5.0.18 Release Date 2026-05-13
	*YP 5.0.19 Build Date 2026-05-26		*YP 5.0.19 Build Date 2026-05-26
	*YP 5.0.19 Release Date 2026-06-05		*YP 5.0.19 Release Date 2026-06-05

Yoann Congal: Typo dashbard -> dashboard

2026-03-09T07:42:21Z

Typo dashbard -> dashboard

← Older revision		Revision as of 07:42, 9 March 2026
Line 8:		Line 8:
	*Yocto Project Patch Review - Thursday 5th Mar. 10am GMT and Monday 9th Mar. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>

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

2026-03-03T15:55:46Z

Yocto Project Status 24 February 2026

← Older revision		Revision as of 15:55, 3 March 2026
Line 1:		Line 1:
	== Yocto Project Status ~~24 February~~ 2026 ==		== Yocto Project Status 3 March 2026 ==
	Current Dev Position: YP 6.0 M2<br/>		Current Dev Position: YP 6.0 M3<br/>
	Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>		Next Deadline: YP 6.0 M3 Build Date 2026-03-09<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~26th Feb~~. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 5th Mar. 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)		*Weekly Project Engineering Sync - Tuesday 3rd Mar. 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)		*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://~~dashboard~~.yoctoproject.org/'''<br/>		'''Project data dashboard: https://dashbard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.33 ~~is due for release~~		*YP 4.0.33 has been released
	*YP 5.0.16 is in QA		*YP 5.0.16 is in TSC review
	*YP 5.3.2 ~~is queued for~~ QA		*YP 6.0 M2, 5.3.2, & 4.0.34 are in QA.
	*~~YP 6~~.~~0 M2 is due to build when we have patches merged~~		**We are aware of changes in QA timelines and are discussing how to address them.
	*We have ~~two open high~~ issues which need further work that will block M3:		*We have issues which need further work that will block M3:
	**x86 kvm broken ~~on Fedora 43 (cpu~~ features ~~issue?)~~ (#16074)		**x86 kvm seemingly broken with certain CPU features (#16074)
	**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)		**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:		*We also have issues we need to resolve before release:
	**Allowing non-destructive git fetcher updates for bitbake-setup		**Allowing non-destructive git fetcher updates for bitbake-setup.
	**Splitting wic into an external tool		**Splitting wic into an external tool.
	**Kernel rust support		**Kernel rust support.
	**Switching to pkg-config		**Switching to pkg-config.
	**Deprecation of ltp (upstream dropped runltp and mandate kirk)		**Deprecation of ltp (upstream dropped runltp and mandate kirk)
	**How to improve DEBUG_BUILD?		**How to improve DEBUG_BUILD?
	**DISTRO_FEATURES ~~changes to ‘nodistro’ in OE-Core~~		**DISTRO_FEATURES defaults improvements.
	**SBOM/cve-check changes		**SBOM/cve-check changes.
	*~~We updated “nodistro” to use 3 of the include files~~ poky ~~was already using:~~		**Reconcile poky and OE-Core defaults templates.
	**Space optimization to ~~reduce build footprint and sstate object size~~		*OE-Core switched to enabling a hash equivalence server by default.
	**Disabling most static libraries by default ~~(build size/speed wins)~~		*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.
	**Enabling security flags by default		*The project has a booth at Embedded World next week, feel free to come and say Hi if you’re there!
	*“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:'''<br/>		'''Ways to contribute:'''<br/>
Line 46:		Line 43:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2893~~ (last week ~~2941~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2908 (last week 2893) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1107~~ (last week ~~1108~~)		**Total patches found: 11063 (last week 1107)
	**Patches in the Pending State: 151 (14%) [last week 151 (14%)]		**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''YP 6.0 Milestone Dates:'''<br/>		'''YP 6.0 Milestone Dates:'''<br/>
	*YP 6.0 M2 ~~Build Date 2026-02-16~~		*YP 6.0 M2 is in QA.
	*YP 6.~~0 M2 Release Date 2026-02-27~~
	*YP 6.0 M3 Build Date 2026-03-09		*YP 6.0 M3 Build Date 2026-03-09
	*YP 6.0 M3 Release Date 2026-03-20		*YP 6.0 M3 Release Date 2026-03-20
Line 61:		Line 57:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.16 ~~Release Date 2026-02-20~~		*YP 5.0.16 is in review.
	*YP 5.3.2 ~~Release Date 2026-02-27~~		*YP 5.3.2 is in QA.
	*YP 4.0.34 ~~Build Date 2026-02-23~~		*YP 4.0.34 is in QA.
	*YP 4.0.~~34 Release Date 2026-03-06~~
	*YP 5.3.3 Build Date 2026-03-09		*YP 5.3.3 Build Date 2026-03-09
	*YP 5.3.3 Release Date 2026-03-20		*YP 5.3.3 Release Date 2026-03-20

Yoann Congal: 5.2.3 -> 5.3.2

2026-02-24T16:03:31Z

5.2.3 -> 5.3.2

← Older revision		Revision as of 16:03, 24 February 2026
Line 13:		Line 13:
	*YP 4.0.33 is due for release		*YP 4.0.33 is due for release
	*YP 5.0.16 is in QA		*YP 5.0.16 is in QA
	*YP 5.2.3 is queued for QA		*YP 5.3.2 is queued for QA
	*YP 6.0 M2 is due to build when we have patches merged		*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:		*We have two open high issues which need further work that will block M3:

Paul Barker: /* Yocto Project Status 24 February 2026 */

2026-02-24T15:23:14Z

Yocto Project Status 24 February 2026

← Older revision		Revision as of 15:23, 24 February 2026
Line 1:		Line 1:
	== Yocto Project Status 17 February 2026 ==		== Yocto Project Status 24 February 2026 ==
	Current Dev Position: YP 6.0 M2<br/>		Current Dev Position: YP 6.0 M2<br/>
	Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>		Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~19th~~ Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 26th 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)		*Weekly Project Engineering Sync - Tuesday 24th 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.33 is ~~awaiting approval~~		*YP 4.0.33 is due for release
	*YP 5.0.16 is in QA		*YP 5.0.16 is in QA
	*YP 6.0 M2 is due to build ~~this week but is blocked by high priority bugs.~~		*YP 5.2.3 is queued for QA
	*~~There are currently 5~~ high ~~open bugs,~~ which will block ~~M2. Three have line of sight to being resolved~~:		*YP 6.0 M2 is due to build when we have patches merged
	**~~rust do_test_compile/do_install segfault~~ (~~#16058~~)		*We have two open high issues which need further work that will block M3:
	**Generation of releases.json needs updating (#~~16138~~)		**x86 kvm broken on Fedora 43 (cpu features issue?) (#16074)
	**AB-INT: ~~do_image_wic: tar command return exit status 2~~ (#~~16143~~)		**AB-INT: opkg-build segmentation fault (memory corruption in pseudo?) (#16078)
	*~~Two are currently needing further work~~:		*We also have issues we need to resolve before release:
	**~~x86 kvm broken on Fedora 43~~ (~~#16074~~)		**Allowing non-destructive git fetcher updates for bitbake-setup
	**AB-~~INT~~: ~~opkg-~~build ~~segmentation fault~~ (~~#16078~~)		**Splitting wic into an external tool
	*~~We removed the bazaar, osc and cvs fetchers since they are obsolete and nobody should be using them~~		**Kernel rust support
	*~~We removed sysvinit compatibility support from systemd images since this will not be supported~~ by ~~upstream during the lifespan of our upcoming LTS release.~~		**Switching to pkg-config
	*~~We removed legacy tls support from openssl in~~ the ~~interests of providing better secure~~ defaults.		**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.		*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.		*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.

Line 40:		Line 46:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2941~~ (last week ~~2973~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2893 (last week 2941) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1108~~ (last week ~~1106~~)		**Total patches found: 1107 (last week 1108)
	**Patches in the Pending State: 151 (14%) [last week ~~152~~ (14%)]		**Patches in the Pending State: 151 (14%) [last week 151 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Line 56:		Line 62:
	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.16 Release Date 2026-02-20		*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 5.3.2 Release Date 2026-02-27
	*YP 4.0.34 Build Date 2026-02-23		*YP 4.0.34 Build Date 2026-02-23

Paul Barker: /* Yocto Project Status 17 February 2026 */

2026-02-17T15:56:26Z

Yocto Project Status 17 February 2026

← Older revision		Revision as of 15:56, 17 February 2026
Line 1:		Line 1:
	== Yocto Project Status 10 February 2026 ==		== Yocto Project Status 17 February 2026 ==
	Current Dev Position: YP 6.0 M2<br/>		Current Dev Position: YP 6.0 M2<br/>
	Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>		Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~12th~~ Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 19th 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)		*Weekly Project Engineering Sync - Tuesday 17th 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 5.3.~~1 was released~~		*YP 4.0.33 is awaiting approval
	*YP 6.0 ~~M1 was released~~		*YP 5.0.16 is in QA
	*YP 4.~~0.33~~ is in QA		*YP 6.0 M2 is due to build this week but is blocked by high priority bugs.
	*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:		*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)		**rust do_test_compile/do_install segfault (#16058)
	**Generation of releases.json needs updating (#16138)		**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:		*Two are currently needing further work:
	**x86 kvm broken on Fedora 43 (#16074)		**x86 kvm broken on Fedora 43 (#16074)
	**AB-INT: opkg-build segmentation fault (#16078)		**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~~		*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.		*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:		*Patch review is now using two branches:
Line 28:		Line 29:
	**“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)		**“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.		*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:'''<br/>		'''Ways to contribute:'''<br/>
Line 40:		Line 40:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2973~~ (last week ~~2945~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2941 (last week 2973) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1106~~ (last week ~~1100~~)		**Total patches found: 1108 (last week 1106)
	**Patches in the Pending State: ~~152~~ (14%) [last week 152 (14%)]		**Patches in the Pending State: 151 (14%) [last week 152 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Line 55:		Line 55:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*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.0.16 Release Date 2026-02-20
	*YP 5.3.2 Build Date 2026-02-16		*YP 5.3.2 Build Date 2026-02-16

Paul Barker: /* Yocto Project Status 10 February 2026 */

2026-02-10T15:43:44Z

Yocto Project Status 10 February 2026

← Older revision		Revision as of 15:43, 10 February 2026
Line 1:		Line 1:
	== Yocto Project Status 3 February 2026==		== Yocto Project Status 10 February 2026 ==
	Current Dev Position: YP 6.0 M2<br/>		Current Dev Position: YP 6.0 M2<br/>
	Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>		Next Deadline: YP 6.0 M2 Build Date 2026-02-16<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~5th~~ Feb. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 12th 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)		*Weekly Project Engineering Sync - Tuesday 10rd 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)		*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/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 5.3.1 ~~is due to be~~ released		*YP 5.3.1 was released
	*YP 6.0 M1 ~~is in QA~~		*YP 6.0 M1 was released
	*YP 4.0.33 is ~~queued for~~ QA ~~after 6.0 M1~~		*YP 4.0.33 is in QA
	*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).~~		*YP 6.0 M2 is due to build next week.
	*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:
	*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)		**Issues reusing binaries from fedora 42/43 on older systems (#16087)
	**~~Hangs of the autobuilder controller (database locking?)~~ (#~~16129~~)		**rust do_test_compile/do_install segfault (#16058)
	**Generation of releases.json needs updating (#16138)		**Generation of releases.json needs updating (#16138)
	*Two are currently needing further work:		*Two are currently needing further work:
	**rust do_test_compile/do_install segfault (#16058)
	**x86 kvm broken on Fedora 43 (#16074)		**x86 kvm broken on Fedora 43 (#16074)
	*~~“build~~-~~sysroots~~: ~~useradd command did not succeed”~~ (#~~16135~~) ~~was fixed, thanks Adrian!~~		**AB-INT: opkg-build segmentation fault (#16078)
	*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~~.		*We are about to drop the 6.12 and 6.16 kernel recipes leaving just 6.18 for the next release
	*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.		*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:'''<br/>		'''Ways to contribute:'''<br/>
Line 37:		Line 40:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2945~~ (last week ~~2978~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2973 (last week 2945) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1100~~ (last week ~~1097~~)		**Total patches found: 1106 (last week 1100)
	**Patches in the Pending State: 152 (14%) [last week 152 (14%)]		**Patches in the Pending State: 152 (14%) [last week 152 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
Line 52:		Line 55:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.1 is under review.		*YP 4.0.33 is in QA.
	*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 Build Date 2026-02-09
	*YP 5.0.16 Release Date 2026-02-20		*YP 5.0.16 Release Date 2026-02-20