Yocto Project - Recent changes [en]

Releases

Thomas Perrot — Thu, 02 Jul 2026 12:34:07 GMT

Release Activity

← Older revision		Revision as of 12:34, 2 July 2026
Line 79:		Line 79:
	\|5.0		\|5.0
	\| April 2024		\| April 2024
	\| 5.0.16 (~~March~~ 2026)		\| 5.0.18 (June 2026)
	\|Long Term Support (until April 2028)		\|Long Term Support (until April 2028)
	\|N/A		\|N/A

2026 Yocto Project Weekly Status Archive

Paul Barker — Tue, 30 Jun 2026 14:48:31 GMT

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

			'''Next Team Meetings:'''<br/>
			*Bug Triage meeting - Thursday 2nd 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)
			*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/>

			'''Key Status/Updates:'''<br/>
			*YP 6.1 M1 was released
			*YP 6.0.2 is in QA
			*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
			*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 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.
			*Intermittent build failures continue to be problematic:
			**several qemu ‘hang’ type issues
			**sometimes yocto-check-layer is showing checksum mismatch issues
			**siggen reset issues (“ResourceWarning: unclosed transport”)
			**groff build race issues
			**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

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

			'''Upcoming development releases:'''<br/>
			*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/>
			*YP 5.0.19
			**Build Date w/c 2026-06-30
			**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

			'''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 23 June 2026 ==		== Yocto Project Status 23 June 2026 ==
	Current Dev Position: YP 6.1 M2<br/>		Current Dev Position: YP 6.1 M2<br/>

Weekly Status

Paul Barker — Tue, 30 Jun 2026 14:47:48 GMT

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