Weekly Status - Revision history

Stephen K. Jolley: /* Yocto Project Status 18 August 2026 */

2026-08-25T14:45:40Z

Yocto Project Status 18 August 2026

← Older revision		Revision as of 14:45, 25 August 2026
Line 1:		Line 1:
	== Yocto Project Status 18 August 2026 ==		== Yocto Project Status 25 August 2026 ==
	Current Dev Position: YP 6.1 M3<br/>		Current Dev Position: YP 6.1 M3<br/>
	Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>		Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~20th~~ Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 27th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~18th~~ Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 25th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~20th~~ Aug. 10am GMT and Monday ~~24th~~ Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 27th Aug. 10am GMT and Monday 31st Aug. 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.1 M3 is due in ~~two weeks~~ and this will be the feature freeze point for YP 6.1.		*YP 6.0.3 is in QA.
			*YP 6.1 M3 is due in one week and this will be the feature freeze point for YP 6.1.
			*For 6.1 M3 our plans are to merge rpm 6, merge openssl 4 and update to the 7.2 kernel. If there are any other major changes planned, please let us know ASAP!
	*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.		*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
	*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.		*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues. It is worth noting that the ‘success’ updates do still need work on the commit message changelogs and much of this work is being pushed to Richard.
	*There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
	*There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
	*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
	*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:		*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
	**Matchbox-wm segfault/xserver restart		**Matchbox-wm segfault/xserver restart
Line 36:		Line 35:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2704~~ (last week ~~2694~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2659 (last week 2704) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1030~~ (last week ~~1028~~)		**Total patches found: 1028 (last week 1030)
	**Patches in the Pending State: 139 (14%) [last week 139 (14%)]		**Patches in the Pending State: 139 (14%) [last week 139 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/
Line 51:		Line 50:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 6.0.3 ~~due to release~~		*YP 6.0.3 is in QA.
	**Release Date w/c 2026-08-24		**Release Date w/c 2026-08-24
	*YP 5.0.20		*YP 5.0.20

Stephen K. Jolley: /* Yocto Project Status 11 August 2026 */

2026-08-18T14:45:55Z

Yocto Project Status 11 August 2026

← Older revision		Revision as of 14:45, 18 August 2026
Line 1:		Line 1:
	== Yocto Project Status 11 August 2026 ==		== Yocto Project Status 18 August 2026 ==
	Current Dev Position: YP 6.1 M3<br/>		Current Dev Position: YP 6.1 M3<br/>
	Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>		Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~13rd~~ Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 20th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~11th~~ Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 18th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~13rd~~ Aug. 10am GMT and Monday ~~17th~~ Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 20th Aug. 10am GMT and Monday 24th Aug. 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.1 M2 has been released		*YP 6.1 M3 is due in two weeks and this will be the feature freeze point for YP 6.1.
	*YP 6.1 M3 is due in ~~three~~ weeks and this will be the feature freeze point for YP 6.1.		*AI scrapers and bots continue to impact the infrastructure, taking huge amounts of time for our sysadmins and with a significant cost impact to the project.
	*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.		*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
	*~~Alex Stewart is stepping down as maintainer~~ of ~~opkg - huge thanks~~ to ~~him for his work on~~ the ~~project over the last 5 years, and thanks to National Instruments/Emerson for their continued support~~ of ~~opkg~~. ~~Maintainership~~ is ~~being handed over to Erick Shepherd (also from NI/Emerson)~~, ~~there~~ is ~~also a call for input and anyone interested~~ in ~~being a co-maintainer~~: https://lists.~~yoctoproject~~.org/g/~~opkg~~/~~topic~~/~~120687514~~		*There have been locking changes with do_fetch/do_unpack within the bitbake fetcher to allow better performance of builds with shared DL_DIRs. There are also performance improvements to the handling of repeated ssl connection queries.
	*~~The NPM fetcher has been re-enabled in bitbake with security improvements~~ and ~~additional test cases~~		*There is discussion on the architecture list about how we could improve the fetcher, particularly around how recursion is handled in git submodules: https://lists.openembedded.org/g/openembedded-architecture/message/2416
	*The upgrade to sbom-cve-check 1.3.3 has more correct handling of Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS assignments. The fallout in OE-core has been handled, other layers may see an uptick in reported CVEs.		*We continue to try and keep up to date with upstream releases through the AUH, big thanks to those sending version updates and fixing version update issues.
	*The SDK_TOOLCHAIN_LANGS variable has been replaced with ~~a more general SDK_FEATURES variable to support improved SDK configurability. Uses of~~ the ~~old variable will need~~ to ~~be updated, `go`~~ and ~~`rust` langs are still supported as SDK features~~.
	*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:		*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
	**Matchbox-wm segfault/xserver restart		**Matchbox-wm segfault/xserver restart
	**aarch64/x86-64 build host contamination/reproducibility issue		**aarch64/x86-64 build host contamination/reproducibility issue
	*We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.		We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
	Remaining intermittent build failures of concern:		*Remaining intermittent build failures of concern:
	**other qemu ‘hang’ type issues on ARM		**other qemu ‘hang’ type issues on ARM
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
Line 37:		Line 36:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2694~~ (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2704 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1028~~ (last week ~~1029~~)		**Total patches found: 1030 (last week 1028)
	**Patches in the Pending State: 139 (14%) [last week ~~141~~ (14%)]		**Patches in the Pending State: 139 (14%) [last week 139 (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 M2: was released.
	*6.1 M3:		*6.1 M3:
	**Build Date: w/c 2026-08-31		**Build Date: w/c 2026-08-31
Line 58:		Line 56:
	**Build Date w/c 2026-08-17		**Build Date w/c 2026-08-17
	**Release Date w/c 2026-08-31		**Release Date w/c 2026-08-31
			*YP 6.0.4
			**Build Date w/c 2026-09-28
			**Release Date w/c 2026-10-12
			*YP 5.0.21
			**Build Date w/c 2026-10-05
			**Release Date w/c 2026-10-19

	*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 4 August 2026 */

2026-08-11T14:46:09Z

Yocto Project Status 4 August 2026

← Older revision		Revision as of 14:46, 11 August 2026
Line 1:		Line 1:
	== Yocto Project Status 4 August 2026 ==		== Yocto Project Status 11 August 2026 ==
	Current Dev Position: YP 6.1 M3<br/>		Current Dev Position: YP 6.1 M3<br/>
	Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>		Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~6th~~ Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 13rd Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~4th~~ Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 11th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~6th~~ Aug. 10am GMT and Monday ~~10th~~ Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 13rd Aug. 10am GMT and Monday 17th Aug. 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.1 M2 is due for ~~release~~		*YP 6.1 M2 has been released
			*YP 6.1 M3 is due in three weeks and this will be the feature freeze point for YP 6.1.
			*We would like to remind everyone that AI-generated code submitted to Yocto Project must include disclosure of the use of AI tools, in line with our policy in the contributor guide (https://docs.yoctoproject.org/contributor-guide/submit-changes.html#acceptance-of-ai-generated-code). Joshua has sent patches adding AGENTS.md files to bitbake and openembedded-core to prompt agents to follow this policy. We are discussing further updates to our policy on AI assisted submissions as this is a rapidly evolving area.
			*Alex Stewart is stepping down as maintainer of opkg - huge thanks to him for his work on the project over the last 5 years, and thanks to National Instruments/Emerson for their continued support of opkg. Maintainership is being handed over to Erick Shepherd (also from NI/Emerson), there is also a call for input and anyone interested in being a co-maintainer: https://lists.yoctoproject.org/g/opkg/topic/120687514
			*The NPM fetcher has been re-enabled in bitbake with security improvements and additional test cases
			*The upgrade to sbom-cve-check 1.3.3 has more correct handling of Ubuntu/Red Hat specific CVEs, which may require new patches or CVE_STATUS assignments. The fallout in OE-core has been handled, other layers may see an uptick in reported CVEs.
			*The SDK_TOOLCHAIN_LANGS variable has been replaced with a more general SDK_FEATURES variable to support improved SDK configurability. Uses of the old variable will need to be updated, `go` and `rust` langs are still supported as SDK features.
	*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:		*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
	**Matchbox-wm segfault/xserver restart		**Matchbox-wm segfault/xserver restart
	**aarch64/x86-64 build host contamination/reproducibility issue		**aarch64/x86-64 build host contamination/reproducibility issue
	We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.		*We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
	*Remaining intermittent build failures of concern:		Remaining intermittent build failures of concern:
	**other qemu ‘hang’ type issues on ARM		**other qemu ‘hang’ type issues on ARM
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
	**siggen reset issues (“ResourceWarning: unclosed transport”)
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
	*Some class cleanups were merged which did require tweaks to some metadata:
	**https://lore.kernel.org/openembedded-core/20260802102854.3952760-1-richard.purdie@linuxfoundation.org/
	**See the “The series does break some things, notably” section
	*Some invasive LICENSE changes have merged into master:
	**We now require the LICENSE field to match SPDX identifiers.
	**The build will issue warnings when this isn’t the case.
	**Non SPDX licenses will need to be of the form LicenseRef-XXX
	**CLOSED is no longer a valid value.
	**‘WITH’ license exceptions are now supported
	~~Big thanks to Joshua for getting us to the point where we can finally clean this up!~~
	*We continue to work on the backlog of patches which has slightly reduced and we’re trying to catch up with AUH updates.
	*Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.
	*Rust is now using a shared work directory which reduces disk usage significantly.
	*There have been further important fixes in pseudo which were included in the latest upgrade.
	*The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!

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

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD 2694 (last week ~~2689~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2694 (last week 2694) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1029~~ (last week ~~1021~~)		**Total patches found: 1028 (last week 1029)
	**Patches in the Pending State: ~~141~~ (14%) [last week 141 (14%)]		**Patches in the Pending State: 139 (14%) [last week 141 (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 M2: ~~due for release~~		*6.1 M2: was released.
	**Release Date: w/c 2026-08-03
	*6.1 M3:		*6.1 M3:
	**Build Date: w/c 2026-08-31		**Build Date: w/c 2026-08-31

Stephen K. Jolley: /* Yocto Project Status 28 July 2026 */

2026-08-04T14:47:55Z

Yocto Project Status 28 July 2026

← Older revision		Revision as of 14:47, 4 August 2026
Line 1:		Line 1:
	== Yocto Project Status ~~28 July~~ 2026 ==		== Yocto Project Status 4 August 2026 ==
	Current Dev Position: YP 6.1 M3<br/>		Current Dev Position: YP 6.1 M3<br/>
	Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>		Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~30th July~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 6th Aug. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~28th July~~ 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 4th Aug. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~30th July~~ 10am GMT and Monday ~~3rd~~ Aug. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 6th Aug. 10am GMT and Monday 10th Aug. 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.19 has been released		*YP 6.1 M2 is due for release
	*YP 6.1 M2 is ~~out of QA and under review~~
	*Progress has been made with some of the AB-INT issues:
	**We identified a kernel issue likely causing the arm psplash boot hangs
	**The groff race issues were reported upstream and we have that section of the build disabled for ~~groff-native now to avoid them~~
	**Several pseudo issues were patched in a recent update
	**One infrastructure issue on a worker was corrected
	*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:		*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
	**Matchbox-wm segfault/xserver restart		**Matchbox-wm segfault/xserver restart
	**aarch64/x86-64 build host contamination/reproducibility issue		**aarch64/x86-64 build host contamination/reproducibility issue
	We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.		We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
			*Remaining intermittent build failures of concern:
			**other qemu ‘hang’ type issues on ARM
			**sometimes yocto-check-layer is showing checksum mismatch issues
			**siggen reset issues (“ResourceWarning: unclosed transport”)
			**intermittent ptest failures in many recipes
			*Some class cleanups were merged which did require tweaks to some metadata:
			**https://lore.kernel.org/openembedded-core/20260802102854.3952760-1-richard.purdie@linuxfoundation.org/
			**See the “The series does break some things, notably” section
	*Some invasive LICENSE changes have merged into master:		*Some invasive LICENSE changes have merged into master:
	**We now require the LICENSE field to match SPDX identifiers.		**We now require the LICENSE field to match SPDX identifiers.
Line 29:		Line 31:
	**‘WITH’ license exceptions are now supported		**‘WITH’ license exceptions are now supported
	Big thanks to Joshua for getting us to the point where we can finally clean this up!		Big thanks to Joshua for getting us to the point where we can finally clean this up!
	*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.		*We continue to work on the backlog of patches which has slightly reduced and we’re trying to catch up with AUH updates.
	*We continue to work on the backlog of patches which has slightly reduced.		*Toolchain upgrades merged to glibc and bintuils with many other recipe version updates too.
	*~~Fixes~~ merged to ~~handle ptest reports for both~~ glibc and ~~musl~~ in ~~resulttool and whilst this improves the main reports, it does cause noise~~ in the ~~regression reports due to poor comparison baselines~~.		*Rust is now using a shared work directory which reduces disk usage significantly.
	*~~Remaining intermittent~~ build ~~failures of concern:~~		*There have been further important fixes in pseudo which were included in the latest upgrade.
	**other qemu ‘hang’ type issues on ARM		*The new uninative does not have i686 build host support. This will mean i686 build host support with uninative will no longer be possible out the box when that is merged to the LTS branches. It is unlikely anyone should be using that!
	**sometimes yocto-check-layer is ~~showing checksum mismatch issues~~
	**siggen reset issues (“ResourceWarning: unclosed transport”)
	**intermittent ptest failures in many recipes

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

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2689~~ (last week ~~2719~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2694 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1021~~ (last week ~~1019~~)		**Total patches found: 1029 (last week 1021)
	**Patches in the Pending State: 141 (14%) [last week ~~144~~ (14%)]		**Patches in the Pending State: 141 (14%) [last week 141 (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 M2: ~~out of QA.~~		*6.1 M2: due for release
	**Release Date: w/c 2026-08-03		**Release Date: w/c 2026-08-03
	*6.1 M3:		*6.1 M3:
Line 65:		Line 64:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.19 due to release		*YP 6.0.3 due to release
	**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		**Release Date w/c 2026-08-24
	*YP 5.0.20		*YP 5.0.20

Stephen K. Jolley: /* Yocto Project Status 21 July 2026 */

2026-07-28T14:48:01Z

Yocto Project Status 21 July 2026

← Older revision		Revision as of 14:48, 28 July 2026
Line 1:		Line 1:
	== Yocto Project Status 21 July 2026 ==		== Yocto Project Status 28 July 2026 ==
	Current Dev Position: YP 6.1 M2<br/>		Current Dev Position: YP 6.1 M3<br/>
	Next Deadline: YP 6.1 M2: w/c 2026-07-20<br/>		Next Deadline: YP 6.1 M3: w/c 2026-08-31<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday ~~23rd~~ July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 30th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~21st~~ July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 28th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~23rd~~ July 10am GMT and Monday ~~27th July~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 30th July 10am GMT and Monday 3rd Aug. 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.2 has been released		*YP 5.0.19 has been released
	*YP 5.~~0.19~~ is ~~due~~ to ~~release~~		*YP 6.1 M2 is out of QA and under review
	*~~YP 6~~.~~1 M2 will~~ build ~~this week after pseudo~~, ~~systemd~~ and ~~resulttool changes merge~~		*Progress has been made with some of the AB-INT issues:
			**We identified a kernel issue likely causing the arm psplash boot hangs
			**The groff race issues were reported upstream and we have that section of the build disabled for groff-native now to avoid them
			**Several pseudo issues were patched in a recent update
			**One infrastructure issue on a worker was corrected
			*There are two AB-INT issues which are in a position where others could now help, as detailed in https://lists.openembedded.org/g/openembedded-core/message/242105:
			**Matchbox-wm segfault/xserver restart
			**aarch64/x86-64 build host contamination/reproducibility issue
			We get a lot of comments about these being hard to reproduce or work on, in both cases, these have specific well defined things which need to be done and a basic understanding of what the issue relates to, if not the actual fix.
	*Some invasive LICENSE changes have merged into master:		*Some invasive LICENSE changes have merged into master:
	**We now require the LICENSE field to match SPDX identifiers.		**We now require the LICENSE field to match SPDX identifiers.
Line 20:		Line 28:
	**CLOSED is no longer a valid value.		**CLOSED is no longer a valid value.
	**‘WITH’ license exceptions are now supported		**‘WITH’ license exceptions are now supported
	Big thanks ~~for~~ Joshua for getting us to the point where we can finally clean this up!		Big thanks to Joshua for getting us to the point where we can finally clean this up!
	*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		*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream. Initial results are good, some manual tweaking of commit messages may be needed, feedback is welcome to improve the automation.
	*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.		*We continue to work on the backlog of patches which has slightly reduced.
	*A couple of ~~further pseudo related issues were identified~~, ~~one with linkat flags and one with openat2 (tar related/triggered). We hope~~ to ~~have patches merged soon~~.		*Fixes merged to handle ptest reports for both glibc and musl in resulttool and whilst this improves the main reports, it does cause noise in the regression reports due to poor comparison baselines.
	*~~Systemd issues with older host kernels (e.g. RHEL 8) is still being worked~~ on ~~https://lists~~.~~openembedded.org/g/openembedded-architecture/topic/119870359~~		*Remaining intermittent build failures of concern:
	*~~We’re working through~~ the ~~backlog of patches~~, the ~~bandwidth for changes needing in depth review/feedback continues~~ to ~~be a challenge. The review calls are running out of time each meeting which limits progress~~.		**other qemu ‘hang’ type issues on ARM
	**We’re making little progress on intermittent build failures ~~despite the problems continuing to impact test builds~~:
	**~~several~~ qemu ‘hang’ type issues on ARM
	**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
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
	*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

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

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2719~~ (last week ~~2689~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2689 (last week 2719) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1019~~ (last week 1019+)		**Total patches found: 1021 (last week 1019)
	**Patches in the Pending State: ~~144~~ (14%) [last week ~~145~~ (14%)]		**Patches in the Pending State: 141 (14%) [last week 144 (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 M2:		*6.1 M2: out of QA.
	**Build Date: w/c 2026-07-20
	**Release Date: w/c 2026-08-03		**Release Date: w/c 2026-08-03
	*6.1 M3:		*6.1 M3:

Stephen K. Jolley: /* Yocto Project Status 14 July 2026 */

2026-07-21T14:50:21Z

Yocto Project Status 14 July 2026

← Older revision		Revision as of 14:50, 21 July 2026
Line 1:		Line 1:
	== Yocto Project Status 14 July 2026 ==		== Yocto Project Status 21 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 ~~16th~~ July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 23rd July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~14th~~ July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 21st July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~16th~~ July 10am GMT and Monday ~~20th~~ July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 23rd July 10am GMT and Monday 27th 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.2 ~~is due to release~~		*YP 6.0.2 has been released
	*YP 5.0.19 is ~~in review~~		*YP 5.0.19 is due to release
	*M2 is ~~next week~~!		*YP 6.1 M2 will build this week after pseudo, systemd and resulttool changes merge
			*Some invasive LICENSE changes have merged into master:
			**We now require the LICENSE field to match SPDX identifiers.
			**The build will issue warnings when this isn’t the case.
			**Non SPDX licenses will need to be of the form LicenseRef-XXX
			**CLOSED is no longer a valid value.
			**‘WITH’ license exceptions are now supported
			Big thanks for Joshua for getting us to the point where we can finally clean this up!
	*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 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 happy~~ to ~~report we worked with Free BSD upstream and~~ have ~~resolved the NFS open/lock issue with a kernel patch that was impacting the autobuilder~~.		*Patches generated by the automatic upgrade helper (AUH) now include changelogs where these can be extracted from upstream.
			*A couple of further pseudo related issues were identified, one with linkat flags and one with openat2 (tar related/triggered). We hope to have patches merged soon.
	*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359		*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’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge. The review calls are running out of time each meeting which limits progress.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		**We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
	*The ~~layer.conf changes~~ are ~~likely to be deferred to 6.2 due to lack~~ of time ~~to gather community consensus before feature freeze~~.
	*We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
	**several qemu ‘hang’ type issues on ARM		**several qemu ‘hang’ type issues on ARM
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
Line 26:		Line 32:
	**groff build race issues		**groff build race issues
	**intermittent ptest failures in many recipes		**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~~		*For the qemuarmv5 amba crash (#16217), we did confirm it doesn’t seem to be load or memory usage related and does seem to happen on the autobuilder but not on other systems, for reasons still currently unknown.

	'''Ways to contribute:'''<br/>		'''Ways to contribute:'''<br/>
Line 38:		Line 44:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2689~~ (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2719 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: 1019 (last week ~~1037~~)		**Total patches found: 1019 (last week 1019+)
	**Patches in the Pending State: ~~145~~ (14%) [last week 145 (14%)]		**Patches in the Pending State: 144 (14%) [last week 145 (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 6.0.~~2 is~~ due to release		*YP 5.0.19 due to release
	**Release Date w/c 2026-07-06
	*YP 5.0.19 is in review
	**Release Date w/c 2026-07-13		**Release Date w/c 2026-07-13
	*YP 6.0.3		*YP 6.0.3

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

2026-07-14T14:44:46Z

Yocto Project Status 7 July 2026

← Older revision		Revision as of 14:44, 14 July 2026
Line 1:		Line 1:
	== Yocto Project Status 7 July 2026 ==		== Yocto Project Status 14 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 ~~9th~~ July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 16th July 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~7th~~ July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 14th July 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~9th~~ July 10am GMT and Monday ~~13th~~ July 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 16th July 10am GMT and Monday 20th 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.1 M1 was released		*YP 6.0.2 is due to release
	*YP 6.0.2 is ~~in review~~		*YP 5.0.19 is in review
	*YP 5.0.19 is in QA		*M2 is next week!
	*~~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 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)~~.		*We are happy to report we worked with Free BSD upstream and have resolved the NFS open/lock issue with a kernel patch that was impacting the autobuilder.
	*Systemd issues with older host kernels (e.g. RHEL 8) is still being worked on https://lists.openembedded.org/g/openembedded-architecture/topic/119870359		*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 have become aware we should ideally replace eudev with a minimal udev build from systemd instead similar to what some other distros are doing.
	*We continue to see high load on our infrastructure due to bots and AI scraping. This has primarily caused timeouts and errors accessing git.openembedded.org & git.yoctoproject.org. We have mitigations in place for now. Traditional git:// protocol continues to be disabled.
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge.		*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~~.		*The layer.conf changes are likely to be deferred to 6.2 due to lack of time to gather community consensus before feature freeze.
	*~~Intermittent~~ build failures ~~continue~~ to ~~be problematic~~:		*We’re making little progress on intermittent build failures despite the problems continuing to impact test builds:
	**several qemu ‘hang’ type issues		**several qemu ‘hang’ type issues on ARM
	**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”)
Line 40:		Line 38:

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2647~~ (last week ~~2620~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2689 (last week 2689) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1036~~ (last week ~~1054~~)		**Total patches found: 1019 (last week 1037)
	**Patches in the Pending State: 145 (14%) [last week 145 (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/
Line 58:		Line 56:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.19 is in ~~QA.~~		*YP 6.0.2 is due to release
			**Release Date w/c 2026-07-06
			*YP 5.0.19 is in review
	**Release Date w/c 2026-07-13		**Release Date w/c 2026-07-13
	*YP 6.0.3		*YP 6.0.3

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/