Yocto Project - Recent changes [en]

Releases

2026-04-24T13:06:12Z

← 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

2026-04-24T09:49:57Z

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

2026-04-24T09:17:13Z

← 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

2026-04-24T07:46:27Z

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

2026-04-23T14:37:03Z

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])