Yocto Project - Recent changes [en]

Releases

MichaelHalstead — Tue, 12 May 2026 20:11:15 GMT

Release Activity: update for 6.0 release

← Older revision		Revision as of 20:11, 12 May 2026
Line 23:		Line 23:
	! Maintainer		! Maintainer
	!Notes		!Notes
			\|-
			\|TBD
			\|6.1
			\| October 2026
			\|
			\|Support for 6 months (until April 2027)
			\|N/A
			\|2.19
			\|Richard Purdie <richard.purdie@linuxfoundation.org>
			\|
	\|-		\|-
	\|Wrynose <br/>(like 'rhinos')		\|Wrynose <br/>(like 'rhinos')
	\|6.0		\|6.0
	\| April 2026		\| April 2026
	\|		\|6.0 (May 2026)
	\|Long Term Support (until April 2030)		\|Long Term Support (until April 2030)
	\|N/A		\|N/A
	\|2.18		\|2.18
	\|~~Richard Purdie~~ <~~richard~~.~~purdie~~@~~linuxfoundation~~.~~org~~>		\|Yoann Congal <yoann.congal@smile.fr>
	\|		\|
	\|-		\|-

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 12 May 2026 14:45:36 GMT

Yocto Project Status 5 May 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 5 May 2026 ==
 Current Dev Position: YP 6.1 M1<br/>
@@ Line 47: / Line 95: @@
 '''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 28 April 2026 ==
 Current Dev Position: YP 6.0 M4<br/>

Weekly Status

Stephen K. Jolley — Tue, 12 May 2026 14:45:23 GMT

Yocto Project Status 5 May 2026

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

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

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

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.35 was released		*YP 5.3.4 is due to release (has been approved)
	*YP 5.3.4 is due to release~~, pending TSC approval~~		*YP 6.0 is due to release (has been approved)
	*YP 6.0 is due to release~~, pending TSC approval~~
	*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
	*Intermittent build failures continue to be problematic		*Intermittent build failures continue to be problematic
	*~~Patch review~~/~~merging is slow due to public holidays clashing with a review call~~		*We have pruned the release artefacts, please let us know if any you would like to use are missing. We’re also interested to know which ones people actually use outside of uninative/buildtools and the BSP test images.
	*Master is open for new development.		*Master is open for new development
			*We would like to know what people are planning to work on for Yocto Project 6.1 and beyond. Please send proposals to the mailing list or raise them during the weekly status call, Paul will be collecting these into a project roadmap.

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

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

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

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 05 May 2026 14:46:17 GMT

Yocto Project Status 28 April 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 28 April 2026 ==
 Current Dev Position: YP 6.0 M4<br/>
@@ Line 50: / Line 98: @@
 '''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 21 April 2026 ==

Weekly Status

Stephen K. Jolley — Tue, 05 May 2026 14:45:53 GMT

Yocto Project Status 28 April 2026

← Older revision		Revision as of 14:45, 5 May 2026
Line 1:		Line 1:
	== Yocto Project Status ~~28 April~~ 2026 ==		== Yocto Project Status 5 May 2026 ==
	Current Dev Position: YP 6.~~0 M4~~<br/>		Current Dev Position: YP 6.1 M1<br/>
	Next Deadline: YP 6.~~0 Release Date~~ w/c 2026-05-04<br/>		Next Deadline: YP 6.1 M1: w/c 2026-06-22<br/>

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

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

	'''Key Status/Updates:'''<br/>		'''Key Status/Updates:'''<br/>
	*YP 4.0.35 ~~is due to release~~		*YP 4.0.35 was released
	*YP 5.3.4 is ~~in QA~~		*YP 5.3.4 is due to release, pending TSC approval
	*YP 6.0 ~~rc1~~ is ~~in QA~~		*YP 6.0 is due to release, pending TSC approval
	*There will be no patch review on Monday 4th May due to ~~public holidays.~~		*We’re working through the backlog of patches, the bandwidth for changes needing in depth review/feedback continues to be a challenge
	*~~We continue to triage~~ the ~~CVEs being reported by~~ the ~~new tooling.~~		*Intermittent build failures continue to be problematic
	*There were some last minute changes ~~to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.~~		*Patch review/merging is slow due to public holidays clashing with a review call
	*There have been several issues in ~~pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1~~ to ~~pull these in.~~		*Master is open for new development.
	*There have been issues with 403 errors from crates.io, there is a ~~change in bitbake to use the preferred upstream urls via their CDN.~~
	*~~The kvm cpu features issue looks~~ to be ~~a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.~~
	*~~git:/~~/ ~~protocol access to git.yoctoproject.org and git.openembeded.org~~ is ~~deprecated and going forward https:// URLs should be used~~ to ~~access git repositories. We are aiming to discontinue git protocol use.~~
	*~~We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle~~ for ~~bandwidth for changes needing in depth review/feedback but are trying to clear the backlog~~.

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

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

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 4.0.35 is in review.		*YP 5.3.4 is due to release, pending TSC approval
	*YP 5.3.4 is ~~in QA~~
	**Release Date 2026-05-06
	*YP 5.0.18		*YP 5.0.18
	**Build Date 2026-05-11		**Build Date 2026-05-11
	**Release Date 2026-05-25		**Release Date 2026-05-25
			*YP 6.0.1
			**Build Date 2026-05-18
			**Release Date 2026-06-01
	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

2026 Yocto Project Weekly Status Archive

Paul Barker — Tue, 28 Apr 2026 14:52:41 GMT

← Older revision		Revision as of 14:52, 28 April 2026
Line 1:		Line 1:
			== Yocto Project Status 28 April 2026 ==
			Current Dev Position: YP 6.0 M4<br/>
			Next Deadline: YP 6.0 Release Date w/c 2026-05-04<br/>

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

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

			'''Key Status/Updates:'''<br/>
			*YP 4.0.35 is due to release
			*YP 5.3.4 is in QA
			*YP 6.0 rc1 is in QA
			*There will be no patch review on Monday 4th May due to public holidays.
			*We continue to triage the CVEs being reported by the new tooling.
			*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
			*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
			*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
			*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
			*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
			*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.

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

			'''Upcoming dot releases:'''<br/>
			*YP 4.0.35 is in review.
			*YP 5.3.4 is in QA
			**Release Date 2026-05-06
			*YP 5.0.18
			**Build Date 2026-05-11
			**Release Date 2026-05-25
			*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 21 April 2026 ==		== Yocto Project Status 21 April 2026 ==
	Current Dev Position: YP 6.0 M4<br/>		Current Dev Position: YP 6.0 M4<br/>

Weekly Status

Paul Barker — Tue, 28 Apr 2026 14:51:47 GMT

Yocto Project Status 28 April 2026

← Older revision		Revision as of 14:51, 28 April 2026
(One intermediate revision by the same user not shown)
Line 1:		Line 1:
	== Yocto Project Status 21 April 2026 ==		== Yocto Project Status 28 April 2026 ==
	Current Dev Position: YP 6.0 M4<br/>		Current Dev Position: YP 6.0 M4<br/>
	Next Deadline: YP 6.0 ~~M4 Build~~ Date 2026-04~~-20~~<br/>		Next Deadline: YP 6.0 Release Date w/c 2026-05-04<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday Apr. ~~23rd~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday 30th Apr. 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday Apr. ~~21st~~ 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday 29th Apr. 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday Apr. ~~23rd~~ 10am GMT ~~and Monday Apr. 27th 9am PDT~~ (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday 30th Apr. 10am GMT (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.~~17 was released~~		*YP 4.0.35 is due to release
	*YP 6.~~0 M3 was released~~		*YP 5.3.4 is in QA
	*YP 4~~.0.35~~ is in QA		*YP 6.0 rc1 is in QA
	*YP 6.0 M4 is due to ~~build~~		*There will be no patch review on Monday 4th May due to public holidays.
	*We continue to triage the CVEs being reported by the new tooling.		*We continue to triage the CVEs being reported by the new tooling.
	*~~Various fixes have merged or are planned~~ to ~~merge before the M4 release build:~~		*There were some last minute changes to DISTRO_FEATURES behaviour to resolve some usability issues that users identified.
	**Various CVE issue resolutions from CVE triage		*There have been several issues in pseudo identified and these have been fixed in the various pseudo point releases. We will upgrade pseudo in 6.0.1 to pull these in.
	**Reproducibility issues with ~~strace/apr-util~~		*There have been issues with 403 errors from crates.io, there is a change in bitbake to use the preferred upstream urls via their CDN.
	**Make race in ~~groff~~		*The kvm cpu features issue looks to be a host system CPU microcode issue and using the latest microcode appears to have resolved the issues.
	**Shadow-native tallylog issue ~~fix~~		*git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
	**Upgrade of barebox to ~~align with an LTS release~~		*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback but are trying to clear the backlog.
	**Implementation of a ~~wrapper for openat2, fixing Fedora 44 beta build failures~~
	**Sbom-cve-check upgrade (along with dependencies)
	*Issues still pending:
	**32bit x86 kvm seemingly broken with certain CPU ~~features (#16074)~~
	**Intermittent qemu boot failures of qemuarmv5 (and ~~possibly qemuarm) since~~ the ~~last kernel upgrade~~
	**Intermittent wic failures on the ~~autobuilder~~
	*~~At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them~~
	git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
	*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback~~. This could impact features making it into~~ the ~~LTS.~~
	*The final whinlatter build is happening this week.

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

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

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.17 was released.		*YP 4.0.35 is in review.
	*YP 4.0.35 is in QA.		*YP 5.3.4 is in QA
	*YP 5.3.4
	**Build Date 2026-04-20
	**Release Date 2026-05-06		**Release Date 2026-05-06
			*YP 5.0.18
			**Build Date 2026-05-11
			**Release Date 2026-05-25
	*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar		*For future release dates, see https://wiki.yoctoproject.org/wiki/Release_calendar

Releases

Paul Barker — Fri, 24 Apr 2026 13:06:12 GMT

← Older revision		Revision as of 13:06, 24 April 2026
Line 4:		Line 4:

	This page remains as it currently contains more information.		This page remains as it currently contains more information.

			See [[Release calendar]] for upcoming release dates.

	== Release Activity==		== Release Activity==
Line 367:		Line 369:
	\|}		\|}

	'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[~~Planning~~]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.		'''Note:''' see also [[Stable Release and LTS]], [[Linux Yocto]], [[Release calendar]] and [[Release Feature Table]] pages. EOL means some community support on email lists but no commit updates in the repos. There is also OS Vendor support for some Yocto EOL releases.

	¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.		¹ The 3.1 series and 4.0 were originally planned for two years but extended to four. Future LTS releases are planned for 4 years.

Yocto Project Release Checklist

Agodard — Fri, 24 Apr 2026 09:49:57 GMT

Add links to changes

← Older revision		Revision as of 09:49, 24 April 2026
Line 41:		Line 41:
	** docs.yoctoproject.org updated correct dropdown version.		** docs.yoctoproject.org updated correct dropdown version.
	** Files to update in yocto-docs:		** Files to update in yocto-docs:
	*** Create new release note templates in documentation/migration-guides/		*** Create new release note templates in documentation/migration-guides/ (e.g. https://lore.kernel.org/yocto-docs/20251218-release-notes-templates-6-0-v1-1-61690583cef2@bootlin.com/)
	*** Update documentation/ref-manual/svg/releases.svg		*** Update documentation/ref-manual/svg/releases.svg (e.g. https://lore.kernel.org/yocto-docs/20251204-release-updates-v2-2-04ca6c26ddd5@bootlin.com/)
	** Files to update in yocto-autobuilder2:		** Files to update in yocto-autobuilder2:
	*** update workers_prev_releases in config.py		*** update workers_prev_releases in config.py (e.g. https://lore.kernel.org/yocto-patches/20251217-add-whinlatter-to-config-v1-1-9aeb42d212bd@bootlin.com/)
	** Files to update in yocto-autobuilder-helper:		** Files to update in yocto-autobuilder-helper:
	*** Update scripts/release-parser.py		*** Update scripts/release-parser.py
	** Files to update in yocto-metrics:		** Files to update in yocto-metrics:
	*** Update patch-status/releases.csv		*** Update patch-status/releases.csv

Yocto Project Release Checklist

Paul Barker — Fri, 24 Apr 2026 09:17:13 GMT

← Older revision		Revision as of 09:17, 24 April 2026
(2 intermediate revisions by the same user not shown)
Line 20:		Line 20:

	* Prior to build of the first release candidate		* Prior to build of the first release candidate
	** Is DISTRO_VERSION updated in poky.conf?		** Is DISTRO_VERSION updated in poky.conf? (e.g. https://git.yoctoproject.org/meta-yocto/commit/?h=wrynose&id=904846ae078ee20de073040ebb77c86e19250f56)
	** Is ~~SDK_VERSION~~ updated in poky.conf?		** Is SANITY_TESTED_DISTROS updated in poky.conf? (e.g. see above)
	** Is ~~SANITY_TESTED_DISTROS~~ updated ~~in poky~~.~~conf~~?		** Is bitbake version updated? (e.g. https://git.openembedded.org/bitbake/commit/?h=2.18&id=33581c84f3a85008239acbd940501a35de48dc91)
	** Are yocto-docs merged to the release branch?		** Are yocto-docs merged to the release branch?
	** Has bitbake -f -c distrodata universe been run?		** Has bitbake -f -c distrodata universe been run?
	** Add a new bitbake-setup configuration file in BitBake's registry (create a new one, do not delete old ones)		** Add a new bitbake-setup configuration file in BitBake's registry (create a new one, do not delete old ones, e.g. https://lore.kernel.org/bitbake-devel/20260422095624.241708-1-richard.purdie@linuxfoundation.org/T/)
			** Add branch selectors and scheduled jobs to autobuilder configuration (e.g. https://lore.kernel.org/yocto-patches/20260423214412.2387367-2-richard.purdie@linuxfoundation.org/T/)
			** Update Toaster fixtures files
			** Update SRCREVs in build-appliance-image (e.g. https://git.openembedded.org/openembedded-core/commit/?h=wrynose&id=42fa856a00ac16b2a7a83d7ecfa60a5be192b16c)

	* After the final release candidate has returned from QA and is approved, verify the following:		* After the final release candidate has returned from QA and is approved, verify the following:

Yocto Project Release Checklist

Agodard — Fri, 24 Apr 2026 07:46:27 GMT

Update the page to remove deprecated content and add other locations in the code to update

← Older revision		Revision as of 07:46, 24 April 2026
Line 1:		Line 1:
	Major Release		Major Release

	- Week prior to build of release candidate		* Week prior to build of release candidate
	- Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle		** Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle
	- wic		*** wic
	- meta-yocto-bsp		*** meta-yocto-bsp
	- meta-yocto		*** meta-yocto
	- linux-firmware		*** linux-firmware
	- bootloaders (grub, syslinux, u-boot, gummiboot, etc..)		*** bootloaders (grub, syslinux, u-boot, gummiboot, etc..)
	- hwdata		*** hwdata
	- pciutils		*** pciutils
	- util-linux		*** util-linux
	- i2c-tools		*** i2c-tools
	- alsa		*** alsa
	- graphics drivers		*** graphics drivers
	- cryptodev		*** cryptodev
	- systemtap		*** systemtap
	- perf		*** perf
	- linux-yocto		*** linux-yocto

	- Prior to build of the first release candidate		* Prior to build of the first release candidate
	- Is DISTRO_VERSION updated in poky.conf?		** Is DISTRO_VERSION updated in poky.conf?
	- Is SDK_VERSION updated in poky.conf?		** Is SDK_VERSION updated in poky.conf?
	- Is SANITY_TESTED_DISTROS updated in poky.conf?		** Is SANITY_TESTED_DISTROS updated in poky.conf?
	- Are yocto-docs merged to the release branch?		** Are yocto-docs merged to the release branch?
	- Has bitbake -f -c distrodata universe been run?		** Has bitbake -f -c distrodata universe been run?
	- ~~Has an updated distro_alias.inc patch been accepted?~~		** Add a new bitbake-setup configuration file in BitBake's registry (create a new one, do not delete old ones)

	- After the final release candidate has returned from QA and is approved, verify the following:		* After the final release candidate has returned from QA and is approved, verify the following:
	- BSP tarballs have been generated.		** BSP tarballs have been generated.
	- Release Notes have been created, finalized, and approved.		** Release Notes have been created, finalized, and approved.
	- Release Notes have been signed.		** Release Notes have been signed.
	- Repos have been tagged with correct commit and signature.		** Repos have been tagged with correct commit and signature.
	- The README for each BSP has been checked and updated if necessary.		** The README for each BSP has been checked and updated if necessary.
	- Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.		** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.
	- The kernel.org mirror sync has been triggered and completed successfully.		** The kernel.org mirror sync has been triggered and completed successfully.
	- The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)		** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
	- docs.yoctoproject.org updated correct dropdown version.		** docs.yoctoproject.org updated correct dropdown version.
			** Files to update in yocto-docs:
			*** Create new release note templates in documentation/migration-guides/
			*** Update documentation/ref-manual/svg/releases.svg
			** Files to update in yocto-autobuilder2:
			*** update workers_prev_releases in config.py
			** Files to update in yocto-autobuilder-helper:
			*** Update scripts/release-parser.py
			** Files to update in yocto-metrics:
			*** Update patch-status/releases.csv

Project Users

RossBurton — Thu, 23 Apr 2026 14:37:03 GMT

Products that use the Yocto Project

← Older revision		Revision as of 14:37, 23 April 2026
Line 104:		Line 104:
	* Lightyear 0 solar EV (Telematics Control Unit)		* Lightyear 0 solar EV (Telematics Control Unit)
	* Mellanox Bluefield SmartNIC		* Mellanox Bluefield SmartNIC
			* Pod Point EV chargers
	* [https://new.siemens.com/global/en/products/buildings.html Siemens Smart Infrastructure]: Products for sustainable, efficient and safe buildings		* [https://new.siemens.com/global/en/products/buildings.html Siemens Smart Infrastructure]: Products for sustainable, efficient and safe buildings
	* Sky Glass (clear from sources tarball [http://oss.sky.com/SkyHD/SkyGlass/skyglass_spk.tar.bz2])		* Sky Glass (clear from sources tarball [http://oss.sky.com/SkyHD/SkyGlass/skyglass_spk.tar.bz2])

Contribute to Toaster

David Reyna — Tue, 21 Apr 2026 15:22:44 GMT

← Older revision		Revision as of 15:22, 21 April 2026
Line 24:		Line 24:
	<pre>		<pre>
	$ git clone https://git.openembedded.org/bitbake/		$ git clone https://git.openembedded.org/bitbake/
	$ ./bitbake/bin/bitbake-setup settings set global 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-poky-distro_poky-machine_qemux86-64

2026 Yocto Project Weekly Status Archive

Stephen K. Jolley — Tue, 21 Apr 2026 14:47:17 GMT

Yocto Project Status 14 April 2026

@@ Line 1: / Line 1: @@
 == Yocto Project Status 14 April 2026 ==
 Current Dev Position: YP 6.0 M4<br/>
@@ Line 59: / Line 119: @@
 '''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 7 April 2026 ==
 Current Dev Position: YP 6.0 M3<br/>

Weekly Status

Stephen K. Jolley — Tue, 21 Apr 2026 14:47:01 GMT

Yocto Project Status 14 April 2026

← Older revision		Revision as of 14:47, 21 April 2026
Line 1:		Line 1:
	== Yocto Project Status 14 April 2026 ==		== Yocto Project Status 21 April 2026 ==
	Current Dev Position: YP 6.0 M4<br/>		Current Dev Position: YP 6.0 M4<br/>
	Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>		Next Deadline: YP 6.0 M4 Build Date 2026-04-20<br/>

	'''Next Team Meetings:'''<br/>		'''Next Team Meetings:'''<br/>
	*Bug Triage meeting - Thursday Apr. ~~16th~~ 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)		*Bug Triage meeting - Thursday Apr. 23rd 7:30am PDT (https://zoom.us/j/454367603?pwd=ZGxoa2ZXL3FkM3Y0bFd5aVpHVVZ6dz09)
	*Weekly Project Engineering Sync - Tuesday Apr. ~~14th~~ 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)		*Weekly Project Engineering Sync - Tuesday Apr. 21st 8am PDT (https://zoom.us/j/990892712?pwd=cHU1MjhoM2x6ck81bkcrYjRrcmJsUT09)
	*Yocto Project Patch Review - Thursday Apr. ~~16th~~ 10am GMT and Monday Apr. ~~20th~~ 9am PDT (https://zoom.us/j/97762397148?pwd=1xk0iC9hp9SjEonaTaONwTb6iWry4Eb.1)		*Yocto Project Patch Review - Thursday Apr. 23rd 10am GMT and Monday Apr. 27th 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.17 ~~is due to be~~ released		*YP 5.0.17 was released
	*YP 6.0 M3 ~~is in QA~~		*YP 6.0 M3 was released
	*YP 4.0.35 is ~~queued for~~ QA		*YP 4.0.35 is in QA
	*We have ~~converted over~~ to ~~sbom~~-~~cve~~-~~check and dropped~~ cve-check~~. This has caused a significant increase in CVEs reported, these are being triaged.~~		*YP 6.0 M4 is due to build
	*Issues ~~with~~ pending ~~work needed~~:		*We continue to triage the CVEs being reported by the new tooling.
			*Various fixes have merged or are planned to merge before the M4 release build:
			**Various CVE issue resolutions from CVE triage
			**Reproducibility issues with strace/apr-util
			**Make race in groff
			**Shadow-native tallylog issue fix
			**Upgrade of barebox to align with an LTS release
			**Implementation of a wrapper for openat2, fixing Fedora 44 beta build failures
			**Sbom-cve-check upgrade (along with dependencies)
			*Issues still pending:
	**32bit x86 kvm seemingly broken with certain CPU features (#16074)		**32bit x86 kvm seemingly broken with certain CPU features (#16074)
	**Reports of pseudo errors on Fedora 44 beta related to openat2()
	**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade		**Intermittent qemu boot failures of qemuarmv5 (and possibly qemuarm) since the last kernel upgrade
	**~~Meta-oe cve layer filtering under new tooling (metrics script tweak?)~~		**Intermittent wic failures on the autobuilder
	**Reprodicubility issues ~~with strace/apr-util after gnulib macro changes (patches in testing)~~		*At this point we will likely run the release build as the remaining issues aren’t critical to end users and we have no clear timeframe for resolution of them
	*There was disruption to ~~git services last week due to scraping attacks against the servers. This resulted in connection issues whilst those were mitigated, particularly the git protocol access.~~
	git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.		git:// protocol access to git.yoctoproject.org and git.openembeded.org is deprecated and going forward https:// URLs should be used to access git repositories. We are aiming to discontinue git protocol use.
	*The recent wic changes will need wic support files to be placed in files/wic within layers going forwards.		*We’re working through the backlog of patches and intermittent build failures are still problematic. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.
	*We’re working through the backlog of patches and intermittent build failures are still problematic~~, including the emergence of new issues (newer kernel version?)~~. We continue to struggle for bandwidth for changes needing in depth review/feedback. This could impact features making it into the LTS.		*The final whinlatter build is happening this week.
	*The final ~~kirkstone~~ build ~~has taken place and we’re no longer planning to merge patches on~~ this ~~branch.~~
	*If you have any final patches for whinlatter, please get these sent to the list ASAP.

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

	'''Tracking Metrics:'''<br/>		'''Tracking Metrics:'''<br/>
	*WDD ~~2777~~ (last week ~~2797~~) (https://wiki.yoctoproject.org/charts/combo.html)		*WDD 2790 (last week 2777) (https://wiki.yoctoproject.org/charts/combo.html)
	*OE-Core/Poky Patch Metrics		*OE-Core/Poky Patch Metrics
	**Total patches found: ~~1072~~ (last week ~~1060~~)		**Total patches found: 1078 (last week 1072)
	**Patches in the Pending State: ~~147~~ (14%) [last week ~~148~~ (14%)]		**Patches in the Pending State: 146 (14%) [last week 147 (14%)]
	**https://valkyrie.yocto.io/pub/non-release/patchmetrics/		**https://valkyrie.yocto.io/pub/non-release/patchmetrics/

	~~'''YP 6.0 Milestone Dates:'''<br/>~~
	*YP 6.0 M3 in QA.
	*YP 6.0 M4 Build Date 2026-04-13
	*YP 6.0 M4 Release Date 2026-05-04

	'''Upcoming dot releases:'''<br/>		'''Upcoming dot releases:'''<br/>
	*YP 5.0.17 ~~is in review~~.		*YP 5.0.17 was released.
	*YP 4.0.35 is in QA.		*YP 4.0.35 is in QA.
	*YP 5.3.4		*YP 5.3.4