Yocto Project - Recent changes [en]

Releases

Rpurdie — Thu, 10 Sep 2026 14:27:48 GMT

← Older revision		Revision as of 14:27, 10 September 2026
Line 23:		Line 23:
	! Maintainer		! Maintainer
	!Notes		!Notes
			\|-
			\|Garburn
			\|6.2
			\| April 2027
			\|
			\|Support for 6 months (until October 2027)
			\|N/A
			\|2.22
			\|Richard Purdie <richard.purdie@linuxfoundation.org>
			\|
	\|-		\|-
	\|Blacksail		\|Blacksail
Line 30:		Line 40:
	\|Support for 6 months (until April 2027)		\|Support for 6 months (until April 2027)
	\|N/A		\|N/A
	\|2.19		\|2.20
	\|Richard Purdie <richard.purdie@linuxfoundation.org>		\|Richard Purdie <richard.purdie@linuxfoundation.org>
	\|		\|

2026 Yocto Project Weekly Status Archive

Rpurdie — Tue, 08 Sep 2026 14:41:55 GMT

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

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

			'''Project data dashboard: https://dashboard.yoctoproject.org/'''<br/>

			'''Key Status/Updates:'''<br/>
			* YP 5.0.20 is under review.
			* YP 6.1 M3 is due to build and we are at feature freeze
			* There are issues with changes in bot/AI protection at github.com which are affecting our CI.
			* Most M3 changes have merged, we want to mitigate the github issues before building M3.
			* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
			* 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.
			* 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.
			*Remaining intermittent build failures of concern:
			**other qemu ‘hang’ type issues on ARM
			**sometimes yocto-check-layer is showing checksum mismatch issues
			**intermittent ptest failures in many recipes
			*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

			'''Ways to contribute:'''<br/>
			*We have several open issues for pseudo and limited maintainer time to work on them. Help from someone familiar with systems programming in C would be greatly appreciated. https://bugzilla.yoctoproject.org/buglist.cgi?list_id=661406&priority=High&priority=Medium%2B&product=Pseudo&query_format=advanced&resolution=---
			*There are a large number of intermittent failures on our autobuilder, any help with investigating, reproducing or solving these issues would be welcome! https://valkyrie.yocto.io/pub/non-release/abint/
			*Many recipes in openembedded-core would benefit from a new recipe maintainer. Please look at https://git.openembedded.org/openembedded-core/tree/meta/conf/distro/include/maintainers.inc and see if you can adopt any of the unassigned recipes.
			*For more ways to contribute, see https://docs.google.com/document/d/18oxKWxLorfF813h82mK6yKTIHeBp_-9owFuCWbzgjOk/edit?usp=sharing

			'''New to the project?'''<br/>
			*We have a list of issues we think are good places to start contributing: https://bugzilla.yoctoproject.org/buglist.cgi?quicksearch=NEWCOMER

			'''Tracking Metrics:'''<br/>
			*WDD 2622 (last week 2612) (https://wiki.yoctoproject.org/charts/combo.html)
			*OE-Core/Poky Patch Metrics
			**Total patches found: 1050 (last week 1039)
			**Patches in the Pending State: 136 (13%) [last week 139 (14%)]
			**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

			'''Upcoming development releases:'''<br/>
			*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/>
			*YP 6.0.3 is in review.
			**Release Date w/c 2026-08-24
			*YP 5.0.20 is in QA.
			**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

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


	== Yocto Project Status 1 September 2026 ==		== Yocto Project Status 1 September 2026 ==
	Current Dev Position: YP 6.1 M3<br/>		Current Dev Position: YP 6.1 M3<br/>

Weekly Status

Rpurdie — Tue, 08 Sep 2026 14:41:35 GMT

← Older revision		Revision as of 14:41, 8 September 2026
Line 1:		Line 1:
	== Yocto Project Status 1 September 2026 ==		== Yocto Project Status 8 September 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 ~~3rd~~ Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 10th Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~1st~~ Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 8st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~3rd~~ Sept. 10am GMT and Monday ~~7th~~ Sept. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 10th Sept. 10am GMT and Monday 14th Sept. 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.3 is under review.		* YP 5.0.20 is under review.
	*YP 5.0.20 is in QA.		* YP 6.1 M3 is due to build and we are at feature freeze
	*YP 6.1 M3 is due to build ~~this week~~ and we are at feature freeze		* There are issues with changes in bot/AI protection at github.com which are affecting our CI.
	*~~For 6~~.~~1 M3~~ our ~~current intent is to merge:~~		* Most M3 changes have merged, we want to mitigate the github issues before building M3.
	**rpm 6		* There is a new meta-openjdk layer: https://github.com/amarula/meta-openjdk https://lore.kernel.org/yocto-patches/xBB4.1788187111192557019.ULaN@lists.yoctoproject.org/T/#u
	**openssl 4		* 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.
	**clang 23.1.0		* 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:
	**7.~~2 linux kernel~~		** Matchbox-wm segfault/xserver restart
	*There were bot protection issues on layerindex causing forbidden errors to queries from layerindex code. ~~These have now been resolved and should be working again~~.		** aarch64/x86-64 build host contamination/reproducibility issue
	*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 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 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.		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:
Line 43:		Line 37:

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

Project Users

RossBurton — Mon, 07 Sep 2026 12:17:19 GMT

Others

← Older revision		Revision as of 12:17, 7 September 2026
Line 73:		Line 73:
	* [https://www.rethinkrobotics.com/ Rethink Robotics GmbH]		* [https://www.rethinkrobotics.com/ Rethink Robotics GmbH]
	* [https://rootcommit.com Root Commit]		* [https://rootcommit.com Root Commit]
			* Sennheiser
	* [https://www.siemens.com/ Siemens] (Gold Member)		* [https://www.siemens.com/ Siemens] (Gold Member)
	* [https://www.smile.eu/en/offers/embedded-iot Smile ECS (Silver Member)]		* [https://www.smile.eu/en/offers/embedded-iot Smile ECS (Silver Member)]

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 01 Sep 2026 14:44:12 GMT

Yocto Project Status 25 August 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 25 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>
@@ Line 66: / Line 140: @@
 '''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
 https://wiki.yoctoproject.org/wiki/TSC<br/>
 == Yocto Project Status 18 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>

Weekly Status

Stephen K. Jolley — Tue, 01 Sep 2026 14:43:41 GMT

Yocto Project Status 25 August 2026

← Older revision		Revision as of 14:43, 1 September 2026
Line 1:		Line 1:
	== Yocto Project Status ~~25 August~~ 2026 ==		== Yocto Project Status 1 September 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 ~~27th Aug~~. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 3rd Sept. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday ~~25th Aug~~. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 1st Sept. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday ~~27th Aug~~. 10am GMT and Monday ~~31st Aug~~. 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 3rd Sept. 10am GMT and Monday 7th Sept. 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.3 is in QA.		*YP 6.0.3 is under review.
	*YP 6.1 M3 is due ~~in one~~ week and ~~this will be the~~ feature freeze ~~point for YP 6.1.~~		*YP 5.0.20 is in QA.
	*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!~~		*YP 6.1 M3 is due to build this week and we are at feature freeze
			*For 6.1 M3 our current intent is to merge:
			**rpm 6
			**openssl 4
			**clang 23.1.0
			**7.2 linux kernel
			*There were bot protection issues on layerindex causing forbidden errors to queries from layerindex code. These have now been resolved and should be working again.
	*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 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.		*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 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 24:		Line 31:
	**sometimes yocto-check-layer is showing checksum mismatch issues		**sometimes yocto-check-layer is showing checksum mismatch issues
	**intermittent ptest failures in many recipes		**intermittent ptest failures in many recipes
			*Progress was made on some of the risc-v speed differences in qemu which should help some of the autobuilder intermittent failures, thanks Trevor!

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

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

Line 50:		Line 58:

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 6.0.3 is in QA.		*YP 6.0.3 is in review.
	**Release Date w/c 2026-08-24		**Release Date w/c 2026-08-24
	*YP 5.0.20		*YP 5.0.20 is in QA.
	**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		*YP 6.0.4

Contribute to Toaster

David Reyna — Fri, 28 Aug 2026 16:53:58 GMT

Workflow

← Older revision		Revision as of 16:53, 28 August 2026
Line 26:		Line 26:
	$ ./bitbake/bin/bitbake-setup settings set --global default top-dir-prefix $PWD		$ ./bitbake/bin/bitbake-setup settings set --global default top-dir-prefix $PWD
	$ ./bitbake/bin/bitbake-setup init --non-interactive poky-master poky distro/poky machine/qemux86-64		$ ./bitbake/bin/bitbake-setup init --non-interactive poky-master poky distro/poky machine/qemux86-64
	$ cd bitbake-builds/poky-master~~-poky-distro_poky-machine_qemux86-64~~		$ cd bitbake-builds/poky-master*
	</pre>		</pre>

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 25 Aug 2026 14:46:02 GMT

Yocto Project Status 18 August 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 18 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>
@@ Line 67: / Line 134: @@
 '''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
 https://wiki.yoctoproject.org/wiki/TSC<br/>
 == Yocto Project Status 11 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>

Weekly Status

Stephen K. Jolley — Tue, 25 Aug 2026 14:45:40 GMT

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

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 18 Aug 2026 14:46:33 GMT

Yocto Project Status 11 August 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 11 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>
@@ Line 63: / Line 131: @@
 '''The Yocto Project’s technical governance is through its Technical Steering Committee, more information is available at:'''<br/>
 https://wiki.yoctoproject.org/wiki/TSC<br/>
 == Yocto Project Status 4 August 2026 ==
 Current Dev Position: YP 6.1 M3<br/>

Weekly Status

Stephen K. Jolley — Tue, 18 Aug 2026 14:45:55 GMT

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