Weekly Status - Revision history

Stephen K. Jolley: /* Yocto Project Status 30 June 2026 */

2026-07-07T14:46:30Z

Yocto Project Status 30 June 2026

← Older revision		Revision as of 14:46, 7 July 2026
Line 1:		Line 1:
	== Yocto Project Status ~~30 June~~ 2026 ==		== Yocto Project Status 7 July 2026 ==
	Current Dev Position: YP 6.1 M2<br/>		Current Dev Position: YP 6.1 M2<br/>
	Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>		Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>

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

	'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>		'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>
Line 12:		Line 12:
	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 6.1 M1 was released		*YP 6.1 M1 was released
	*YP 6.0.2 is in QA		*YP 6.0.2 is in review
	*~~The number of open CVEs on scarthgap has been reduced with stable kernel updates merging.~~ We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases, see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383		*YP 5.0.19 is in QA
	*~~Systemd v260+ will require~~ a ~~host Linux kernel of 5~~.~~10 or later due~~ to ~~systemd utils run during the build process~~. ~~This presents~~ issues with ~~RHEL 8 era distros which have~~ older ~~kernel versions~~. ~~We have patches in progress but if you’re using these distros, assistance will be needed to keep them supported~~. ~~See~~ https://lists.openembedded.org/g/openembedded-architecture/topic/119870359		*We are now two weeks away from M2!
			*We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases (affecting master, wrynose and scarthgap), see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
			*We are having some challenges with the autobuilder, both with an NFS server open file/lock build up of some kind causing slowdown and eventual halting of write operations and also a mkdir cache race issue. We are working to debug both issues but it is distracting from other work like patch review and new development (e.g. layer.conf format changes).
			*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
			*We have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
	*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.		*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
			*A key pseudo memory corruption issue when interacting with bash was identified and patches are being worked on for a new pseudo release to address this.
	*Intermittent build failures continue to be problematic:		*Intermittent build failures continue to be problematic:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues
Line 53:		Line 58:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.19		*YP 5.0.19 is in QA.
	**Build Date w/c 2026-06-30
	**Release Date w/c 2026-07-13		**Release Date w/c 2026-07-13
	*YP 6.0.3		*YP 6.0.3
	**Build Date w/c 2026-08-10		**Build Date w/c 2026-08-10
	**Release Date w/c 2026-08-24		**Release Date w/c 2026-08-24
			*YP 5.0.20
			**Build Date w/c 2026-08-17
			**Release Date w/c 2026-08-31

	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

Paul Barker: /* Yocto Project Status 23 June 2026 */

2026-06-30T14:47:48Z

Yocto Project Status 23 June 2026

← Older revision		Revision as of 14:47, 30 June 2026
Line 1:		Line 1:
	== Yocto Project Status 23 June 2026 ==		== Yocto Project Status 30 June 2026 ==
	Current Dev Position: YP 6.1 M2<br/>		Current Dev Position: YP 6.1 M2<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>		Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~25th June~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 2nd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~23rd~~ June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 30th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~25th June~~ 10am GMT and Monday ~~29th June~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 2nd July 10am GMT and Monday 6th July 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.1 was released		*YP 6.1 M1 was released
	*YP 6.~~1 M1~~ is in ~~review~~		*YP 6.0.2 is in QA
	*~~AUH is now running daily in incremental mode. We’re still tweaking some~~ of ~~the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.~~		*The number of open CVEs on scarthgap has been reduced with stable kernel updates merging. We have identified a few linux-yocto CVEs which need triaging due to missing version information in the CVE databases, see the email sent to the list: https://lists.yoctoproject.org/g/yocto/topic/120036383
	*CVE metrics are up on scarthgap ~~& wrynose branches due to delays~~ with kernel ~~upgrades~~. ~~We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg~~ which ~~we needed~~ to ~~handle. We’re working through this~~, ~~help is needed~~ to ~~accelerate testing of future stable kernel upgrades~~.		*Systemd v260+ will require a host Linux kernel of 5.10 or later due to systemd utils run during the build process. This presents issues with RHEL 8 era distros which have older kernel versions. We have patches in progress but if you’re using these distros, assistance will be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
	*Systemd v260 will require Linux 5.10 or later~~. We run some~~ systemd utils ~~on the host~~ during the build~~, so this~~ presents issues with RHEL 8 era distros which have older kernel versions. ~~If you use one of~~ these distros, assistance ~~may~~ be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
	*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.		*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
Line 36:		Line 35:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2620~~ (last week ~~2590~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2647 (last week 2620) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1054~~(last week ~~1061~~)		**Total patches found: 1036 (last week 1054)
	**Patches in the Pending State: 145 (14%) [last week ~~146~~ (14%)]		**Patches in the Pending State: 145 (14%) [last week 145 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''Upcoming development releases:'''<br/>		'''Upcoming development releases:'''<br/>
	*6.1 M1:
	**Build Date: w/c 2026-06-08
	**Release Date: w/c 2026-06-22
	*6.1 M2:		*6.1 M2:
	**Build Date: w/c 2026-07-20		**Build Date: w/c 2026-07-20
Line 57:		Line 53:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 6.0.1 is due to release
	*YP 6.0.2
	**Build Date w/c 2026-06-23
	**Release Date w/c 2026-07-06
	*YP 5.0.19		*YP 5.0.19
	**Build Date w/c 2026-06-30		**Build Date w/c 2026-06-30
	**Release Date w/c 2026-07-13		**Release Date w/c 2026-07-13
			*YP 6.0.3
			**Build Date w/c 2026-08-10
			**Release Date w/c 2026-08-24

	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

Paul Barker at 14:50, 23 June 2026

2026-06-23T14:50:41Z

← Older revision		Revision as of 14:50, 23 June 2026
Line 1:		Line 1:
	== Yocto Project Status 16 June 2026 ==		== Yocto Project Status 23 June 2026 ==
	Current Dev Position: YP 6.1 M2<br/>		Current Dev Position: YP 6.1 M2<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>		Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~18th~~ June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 25th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~16th~~ June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 23rd June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~18th~~ June 10am GMT and Monday ~~22nd~~ June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 25th June 10am GMT and Monday 29th June 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.1 ~~is due for release~~		*YP 6.0.1 was released
	*YP 6.1 M1 is in QA		*YP 6.1 M1 is in review
			*AUH is now running daily in incremental mode. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know. Help is needed with resolving automatic update failures and getting the patches into a state where they can be accepted.
			*CVE metrics are up on scarthgap & wrynose branches due to delays with kernel upgrades. We’ve had intermittent LTP failures, kconfig type changes, lttng build failures and new warnings in dmesg which we needed to handle. We’re working through this, help is needed to accelerate testing of future stable kernel upgrades.
			*Systemd v260 will require Linux 5.10 or later. We run some systemd utils on the host during the build, so this presents issues with RHEL 8 era distros which have older kernel versions. If you use one of these distros, assistance may be needed to keep them supported. See https://lists.openembedded.org/g/openembedded-architecture/topic/119870359
			*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
	*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged		*Intermittent build failures continue to be problematic:
	*AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.		**several qemu ‘hang’ type issues
	*We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
	*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
	*Intermittent build failures continue to be problematic ~~and unchanged from last week~~:
	**several qemu ‘hang’ type issues ~~- the qemu upgrade merged, at least some issues still occur~~
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
	**siggen reset issues (“ResourceWarning: unclosed transport”)		**siggen reset issues (“ResourceWarning: unclosed transport”)
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes ~~(python3-click was tweaked)~~		**intermittent ptest failures in many recipes
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto		*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 37:		Line 36:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2590~~ (last week ~~2655~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2620 (last week 2590) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1061~~ (last week ~~1056~~)		**Total patches found: 1054(last week 1061)
	**Patches in the Pending State: ~~146~~ (14%) [last week ~~147~~ (14%)]		**Patches in the Pending State: 145 (14%) [last week 146 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Paul Barker at 14:47, 16 June 2026

2026-06-16T14:47:04Z

← Older revision		Revision as of 14:47, 16 June 2026
Line 1:		Line 1:
	== Yocto Project Status 9 June 2026 ==		== Yocto Project Status 16 June 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M2<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>		Next Deadline: YP 6.1 M1: w/c 2026-07-20<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~11th~~ June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 18th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~9th~~ June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 16th June. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~11th~~ June 10am GMT and Monday ~~15th~~ June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 18th June 10am GMT and Monday 22nd June 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.18 has been released		*YP 6.0.1 is due for release
	*YP 6.0.1 is ~~in QA.~~		*YP 6.1 M1 is in QA
	*YP 6.1 M1 is ~~due to build this week~~
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
	*~~Patches~~ to remove shell=True subprocess usage ~~have merged~~ in ~~bitbake but~~ OE-Core still ~~needs significant work~~, ~~help would be welcome~~ with ~~this~~.		*An initial round of patches to remove shell=True subprocess usage in OE-Core have now merged
			*AUH is now running daily in incremental mode so we can avoid large batches of upgrade patches and spread them out as well as reacting more quickly to new upstream releases. We’re still tweaking some of the behaviours and reporting but if anyone has feedback/concerns, let us know.
			*We’ve deliberately aimed to get up to date with the AUH success patches to better evaluate the ongoing upgrades.
	*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109		*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
	*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
	*Intermittent build failures continue to be problematic and unchanged from last week:		*Intermittent build failures continue to be problematic and unchanged from last week:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues - the qemu upgrade merged, at least some issues still occur
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
	**siggen reset issues (“ResourceWarning: unclosed transport”)		**siggen reset issues (“ResourceWarning: unclosed transport”)
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes (python3-click was tweaked)
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto		*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto


	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 36:		Line 37:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2655~~ (last week ~~2630~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2590 (last week 2655) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1056~~ (last week ~~1087~~)		**Total patches found: 1061 (last week 1056)
	**Patches in the Pending State: ~~147~~ (14%) [last week 147 (14%)]		**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

Line 57:		Line 58:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 6.0.1 is ~~in QA.~~		*YP 6.0.1 is due to release
	*YP 6.0.2		*YP 6.0.2
	**Build Date w/c 2026-06-23		**Build Date w/c 2026-06-23

Paul Barker: /* Yocto Project Status 9 June 2026 */

2026-06-09T08:13:38Z

Yocto Project Status 9 June 2026

← Older revision		Revision as of 08:13, 9 June 2026
Line 17:		Line 17:
	*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.		*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
	*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109		*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
			*We have changed the xz and zstd decompression dependencies to make the build slightly more efficient and use the host tools for decompression
	*Intermittent build failures continue to be problematic and unchanged from last week:		*Intermittent build failures continue to be problematic and unchanged from last week:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues

Paul Barker: /* Yocto Project Status 9 June 2026 */

2026-06-09T07:08:01Z

Yocto Project Status 9 June 2026

← Older revision		Revision as of 07:08, 9 June 2026
Line 1:		Line 1:
	== Yocto Project Status 2 June 2026 ==		== Yocto Project Status 9 June 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~4th~~ June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 11th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~2nd~~ June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 9th June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~4th~~ June 10am GMT and Monday ~~8th~~ June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 11th June 10am GMT and Monday 15th June 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.18 ~~is due to be~~ released		*YP 5.0.18 has been released
	*YP 6.0.1 is in QA.		*YP 6.0.1 is in QA.
	*YP 6.1 M1 is due to build ~~next~~ week		*YP 6.1 M1 is due to build this week
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
	*~~The upgrade~~ to ~~gcc 16~~ merged		*Patches to remove shell=True subprocess usage have merged in bitbake but OE-Core still needs significant work, help would be welcome with this.
	*We ~~are planning~~ to ~~improve our python subprocess calls~~ to ~~avoid shell=True~~, we ~~would appreciate others following~~ and ~~doing this~~ in ~~their code too~~.		*We have merged support for `devtool upgrade --stable` and the upstream-stable-release-point bbclass. We hope to use this to track upstream projects with known good stable release series, but we need input and discussion on what the criteria should be. Please participate in the discussion on the OE-Architecture list: https://lists.openembedded.org/g/openembedded-architecture/topic/119437109
	*Intermittent build failures continue to be problematic and unchanged from last week:		*Intermittent build failures continue to be problematic and unchanged from last week:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues
Line 23:		Line 23:
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
	*Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
	*The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto		*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto

Line 37:		Line 35:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2630~~ (last week ~~2660~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2655 (last week 2630) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~108~~ (last week ~~1083~~)		**Total patches found: 1056 (last week 1087)
	**Patches in the Pending State: 147 (14%) [last week ~~148~~ (13%)]		**Patches in the Pending State: 147 (14%) [last week 147 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
	7
			'''Upcoming development releases:'''<br/>
			*6.1 M1:
			**Build Date: w/c 2026-06-08
			**Release Date: w/c 2026-06-22
			*6.1 M2:
			**Build Date: w/c 2026-07-20
			**Release Date: w/c 2026-08-03
			*6.1 M3:
			**Build Date: w/c 2026-08-31
			**Release Date: w/c 2026-09-14
			*6.1.0:
			**Build Date (M4): w/c 2026-10-12
			**Release Date: w/c 2026-11-02

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.18 is in review.
	*YP 6.0.1 is in QA.		*YP 6.0.1 is in QA.
	*YP 6.0.2		*YP 6.0.2
	**Build Date 2026-06-23		**Build Date w/c 2026-06-23
	**Release Date 2026-07-06		**Release Date w/c 2026-07-06
	*YP 5.0.19		*YP 5.0.19
	**Build Date 2026-06-30		**Build Date w/c 2026-06-30
	**Release Date 2026-07-13		**Release Date w/c 2026-07-13
	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

Stephen K. Jolley: /* Yocto Project Status 26 May 2026 */

2026-06-02T14:41:30Z

Yocto Project Status 26 May 2026

← Older revision		Revision as of 14:41, 2 June 2026
Line 1:		Line 1:
	== Yocto Project Status ~~26 May~~ 2026 ==		== Yocto Project Status 2 June 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~28th May~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 4th June 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~26th May~~ 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 2nd June 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~28th May~~ 10am GMT and Monday ~~1st~~ June 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 4th June 10am GMT and Monday 8th June 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.18 is ~~out of QA and under review.~~		*YP 5.0.18 is due to be released
	*YP 6.0.1 is in QA		*YP 6.0.1 is in QA.
			*YP 6.1 M1 is due to build next week
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
			*The upgrade to gcc 16 merged
			*We are planning to improve our python subprocess calls to avoid shell=True, we would appreciate others following and doing this in their code too.
	*Intermittent build failures continue to be problematic and unchanged from last week:		*Intermittent build failures continue to be problematic and unchanged from last week:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues
Line 20:		Line 23:
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
	*~~Is anyone using 32 bit SDKs, if so let us know.~~ Qemu dropped support for 32 bit hosts and we are ~~considering discontinuing~~ 32 ~~bit SDKs.~~		*Qemu v11 dropped support for 32 bit hosts and we are likely to drop support for running builds on 32 bits hosts
	*~~We are~~ likely to ~~merge the gcc 16 upgrade soon~~		*The upstream kernel is looking likely to drop x32 support and if they do, we will have to drop our support too - let hem/us know if you’re using it!
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto		*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
	*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 35:		Line 37:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2660~~ (last week ~~2673~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2630 (last week 2660) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1083~~ (last week 1083)		**Total patches found: 108 (last week 1083)
	**Patches in the Pending State: ~~148~~ (14%) [last week 148 (13%)]		**Patches in the Pending State: 147 (14%) [last week 148 (13%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
			7
	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.18 is in review.		*YP 5.0.18 is in review.
	*YP 6.0.1 is in QA.		*YP 6.0.1 is in QA.
			*YP 6.0.2
			**Build Date 2026-06-23
			**Release Date 2026-07-06
	*YP 5.0.19		*YP 5.0.19
	**Build Date 2026-06-30		**Build Date 2026-06-30

Stephen K. Jolley: /* Yocto Project Status 19 May 2026 */

2026-05-26T14:41:49Z

Yocto Project Status 19 May 2026

← Older revision		Revision as of 14:41, 26 May 2026
Line 1:		Line 1:
	== Yocto Project Status 19 May 2026 ==		== Yocto Project Status 26 May 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~21st~~ May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 28th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~19th~~ May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 26th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~21st~~ May 10am GMT and Monday ~~25th May~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 28th May 10am GMT and Monday 1st June 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 ~~was released, thanks everyone who contributed!~~		*YP 5.0.18 is out of QA and under review.
	*YP 5.0.18 is in QA.		*YP 6.0.1 is in QA
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
	*Intermittent build failures continue to be problematic:		*Intermittent build failures continue to be problematic and unchanged from last week:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
Line 20:		Line 20:
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
	*~~Master (blacksail) is open~~ for ~~new development~~		*Is anyone using 32 bit SDKs, if so let us know. Qemu dropped support for 32 bit hosts and we are considering discontinuing 32 bit SDKs.
			*We are likely to merge the gcc 16 upgrade soon
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto		*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
	*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716		*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
	*Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 35:		Line 35:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2673~~ (last week ~~2688~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2660 (last week 2673) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: 1083 (last week ~~1087~~)		**Total patches found: 1083 (last week 1083)
	**Patches in the Pending State: 148 (14%) [last week ~~146~~ (13%)]		**Patches in the Pending State: 148 (14%) [last week 148 (13%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.4 was released.		*YP 5.0.18 is in review.
	*YP 5.0.18 is in QA.		*YP 6.0.1 is in QA.
	*YP 6.0.1
	**Build Date 2026-05-18
	**Release Date 2026-06-01
	*YP 5.0.19		*YP 5.0.19
	**Build Date 2026-06-30		**Build Date 2026-06-30

Stephen K. Jolley: /* Yocto Project Status 12 May 2026 */

2026-05-19T14:47:51Z

Yocto Project Status 12 May 2026

← Older revision		Revision as of 14:47, 19 May 2026
Line 1:		Line 1:
	== Yocto Project Status 12 May 2026 ==		== Yocto Project Status 19 May 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~14th~~ May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 21st May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~12th~~ May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 19th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~14th~~ May 10am GMT and Monday ~~18th~~ May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 21st May 10am GMT and Monday 25th May 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.4 is due to release (has been approved)~~		*YP 6.0 was released, thanks everyone who contributed!
	*YP 6.0 is ~~due to release (has been approved)~~		*YP 5.0.18 is in QA.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.
	*Intermittent build failures continue to be problematic		*Intermittent build failures continue to be problematic:
	*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.		**several qemu ‘hang’ type issues
	*Master is open for new development		**sometimes yocto-check-layer is showing checksum mismatch issues
	*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. ~~Please send proposals to~~ the ~~mailing list~~ or ~~raise them during~~ the ~~weekly status call, Paul~~ will be ~~collecting these into a project roadmap~~.		**siggen reset issues (“ResourceWarning: unclosed transport”)
			**groff build race issues
			**intermittent ptest failures in many recipes
			*Master (blacksail) is open for new development
			*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. We have a roadmap document in Google Docs: https://docs.google.com/document/d/12xgAzSjDj5zVlo4eQIbiv1s3QMjtBTCvBFY3_T7OPto
			*We are updating the project’s security team and welcome nominations and/or feedback: https://lists.openembedded.org/g/openembedded-architecture/topic/119388716
			*Monday 25th May is a public holiday in the UK and USA so there will be no patch review call.

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 29:		Line 35:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2688~~ (last week ~~2698~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2673 (last week 2688) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1087~~ (last week 1087)		**Total patches found: 1083 (last week 1087)
	**Patches in the Pending State: ~~146~~ (13%) [last week 146 (13%)]		**Patches in the Pending State: 148 (14%) [last week 146 (13%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.4 ~~is due to release~~		*YP 5.3.4 was released.
	*YP 5.0.18		*YP 5.0.18 is in QA.
	**Build Date 2026-05-11
	**Release Date 2026-05-25
	*YP 6.0.1		*YP 6.0.1
	**Build Date 2026-05-18		**Build Date 2026-05-18
	**Release Date 2026-06-01		**Release Date 2026-06-01
			*YP 5.0.19
			**Build Date 2026-06-30
			**Release Date 2026-07-13
	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

Stephen K. Jolley: /* Yocto Project Status 5 May 2026 */

2026-05-12T14:45:23Z

Yocto Project Status 5 May 2026

← Older revision		Revision as of 14:45, 12 May 2026
Line 1:		Line 1:
	== Yocto Project Status 5 May 2026 ==		== Yocto Project Status 12 May 2026 ==
	Current Dev Position: YP 6.1 M1<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.1 M1: w/c 2026-06-22<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-08<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~7th~~ May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 14th May 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~5th~~ May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 12th May 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~7th~~ May 10am GMT and Monday ~~11th~~ May 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 14th May 10am GMT and Monday 18th May 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.35 was released		*YP 5.3.4 is due to release (has been approved)
	*YP 5.3.4 is due to release~~, pending TSC approval~~		*YP 6.0 is due to release (has been approved)
	*YP 6.0 is due to release~~, pending TSC approval~~
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
	*Intermittent build failures continue to be problematic		*Intermittent build failures continue to be problematic
	*~~Patch review~~/~~merging is slow due to public holidays clashing with a review call~~		*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
	*Master is open for new development.		*Master is open for new development
			*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 29:		Line 29:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2698~~ (last week ~~2788~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2688 (last week 2698) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: 1087 (last week ~~1085~~)		**Total patches found: 1087 (last week 1087)
	**Patches in the Pending State: 146 (13%) [last week 146 (13%)]		**Patches in the Pending State: 146 (13%) [last week 146 (13%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.3.4 is due to release~~, pending TSC approval~~		*YP 5.3.4 is due to release
	*YP 5.0.18		*YP 5.0.18
	**Build Date 2026-05-11		**Build Date 2026-05-11