Yocto Project Release Process - Revision history

Lee chee yang at 10:23, 6 October 2025

2025-10-06T10:23:20Z

← Older revision		Revision as of 10:23, 6 October 2025
Line 210:		Line 210:

	===== Release of Build =====		===== Release of Build =====
	* Run the release script to stage the release. This is not required from Kirkstone onwards. https://git.yoctoproject.org/release-tools/tree/release.py?h=dunfell-ReleaseProcess . This script will do the following...
	~~- Create the staging directory.~~
	~~- Remove the rpm/deb directories.~~
	~~- Delete duplicate files and extraneous blobs, and convert symlinks.~~
	~~- Rename tarballs to reflect current naming conventions. For example. poky-<githash>.tar.bz2 should be renamed to poky-<release_name>-<release_number>.tar.bz2~~
	~~- Generate the BSP tarballs~~
	~~- Extract the eclipse-plugin archive to http://downloads.yoctoproject.org/releases/eclipse-plugin/<M>.<m> where M.m is the Yocto version~~
	~~- Copy the adt-dev repo to the live site (For release lines prior to 2.0.)~~
	~~- Create the md5sum table for the release~~
	* Copy the staging directory to the downloads directory (not required for Kirkstone onwards)
	* Check the Build log for build issue. Build URL included in build notification email(qa-email).		* Check the Build log for build issue. Build URL included in build notification email(qa-email).
	* Check the testresult and regression report for any issue.		* Check the testresult and regression report for any issue.
	* run https://git.yoctoproject.org/release-tools/tree/testresults.py to combined the manual test result into yocto-testresults. ~~This will~~ create new commit and tag for yocto-testresults. ~~In certain condition this script might break, this can mean something wrong with~~ any ~~artefacts or yocto~~-~~testresults* repo. This will also create~~ testreport.txt		* Once manual test completed:
	* Create release notes, ~~finalize, get approval, and [[GPG sign notes &~~ git ~~tags]].~~		- On autobuilder runner, run https://git.yoctoproject.org/release-tools/tree/testresults.py, this will:
	* create release notes in .rst and send to docs@lists.yoctoproject.org. (for ~~4.0 onwards)~~		- combined the manual test result into yocto-testresults.
	* Check the ~~new documentation~~ for ~~the~~ release ~~is available on docs~~.~~yoctoproject~~.~~org~~ (for 4.0 ~~onward~~)		- create new commit and tag for yocto-testresults
	* Sync the release out to the mirrors.		- create consolidated testreport.txt.
			- check the testreport and report for any issue.
			- add testreport.txt to yocto-testresults-contrib
			* Create release notes (not required for milestone release):
			- On autobuilder runner, run https://git.yoctoproject.org/release-tools/tree/relnotes.py to generate draft for release notes
			- finetune the release note draft
			- get release notes review and approval for release.
			- GPG sign finalized release notes once approved.
			* Tag these repos.
			- bitbake
			- openembedded-core
			- poky
			- meta-gplv2 (for 4.0.x and older series)
			- meta-mingw
			- meta-yocto
			- yocto-docs
			- yocto-testresults
			- yocto-testresults-contrib
			* Sync the release out to the kernel.org mirrors.
	* Once sync out is complete, verify that pages work, and download and documentation links work.		* Once sync out is complete, verify that pages work, and download and documentation links work.
	* ~~Tag the repos~~.		* verify all tags and release notes are correctly tagged and signed, see [[GPG sign notes & git tags]].
	* Verify the items on the RELEASE CHECKLIST: https://wiki.yoctoproject.org/wiki/Yocto_Project_Release_Checklist		* Verify the items on the RELEASE CHECKLIST: https://wiki.yoctoproject.org/wiki/Yocto_Project_Release_Checklist
	* ~~Post~~ release ~~announcement~~ on ~~Blog ( Deprecated ? )~~		* Check the new documentation for the release is available on docs.yoctoproject.org
	* Post release announcement on mailing lists (yocto and yocto-announce)		* Post release announcement on mailing lists (yocto and yocto-announce)
	* ~~Update DISTRO~~ and ~~DISTRO_VERSION in master~~ to ~~be the main release+snapshot~~		* create release notes in .rst and send to docs@lists.yoctoproject.org.

MichaelHalstead: /* Release of Build */

2024-06-07T22:24:35Z

Release of Build

← Older revision		Revision as of 22:24, 7 June 2024
Line 223:		Line 223:
	* Check the testresult and regression report for any issue.		* Check the testresult and regression report for any issue.
	* run https://git.yoctoproject.org/release-tools/tree/testresults.py to combined the manual test result into yocto-testresults. This will create new commit and tag for yocto-testresults. In certain condition this script might break, this can mean something wrong with any artefacts or yocto-testresults* repo. This will also create testreport.txt		* run https://git.yoctoproject.org/release-tools/tree/testresults.py to combined the manual test result into yocto-testresults. This will create new commit and tag for yocto-testresults. In certain condition this script might break, this can mean something wrong with any artefacts or yocto-testresults* repo. This will also create testreport.txt
	* Create release notes, finalize, get approval, and ~~gpg~~ sign.		* Create release notes, finalize, get approval, and [[GPG sign notes & git tags]].
	* create release notes in .rst and send to docs@lists.yoctoproject.org. (for 4.0 onwards)		* create release notes in .rst and send to docs@lists.yoctoproject.org. (for 4.0 onwards)
	* Check the new documentation for the release is available on docs.yoctoproject.org (for 4.0 onward)		* Check the new documentation for the release is available on docs.yoctoproject.org (for 4.0 onward)

Lee chee yang: /* Release of Build */

2023-12-11T08:45:51Z

Release of Build

← Older revision		Revision as of 08:45, 11 December 2023
Line 210:		Line 210:

	===== Release of Build =====		===== Release of Build =====
	* Run the release script to stage the release. ~~http~~://git.yoctoproject.org/~~cgit/cgit.cgi/yocto~~-~~autobuilder~~/tree~~/bin/release_scripts~~/release.py~~. This is not required for Kirkstone onwards~~. This script will do the following...		* Run the release script to stage the release. This is not required from Kirkstone onwards. https://git.yoctoproject.org/release-tools/tree/release.py?h=dunfell-ReleaseProcess . This script will do the following...
	- Create the staging directory.		- Create the staging directory.
	- Remove the rpm/deb directories.		- Remove the rpm/deb directories.
Line 220:		Line 220:
	- Create the md5sum table for the release		- Create the md5sum table for the release
	* Copy the staging directory to the downloads directory (not required for Kirkstone onwards)		* Copy the staging directory to the downloads directory (not required for Kirkstone onwards)
	* ~~Combined~~ the manual test result into yocto-testresults.		* Check the Build log for build issue. Build URL included in build notification email(qa-email).
	* Create release notes, finalize, get approval, and gpg sign.		* Check the testresult and regression report for any issue.
	* Check the new documentation for the release is available on docs.yoctoproject.org		* run https://git.yoctoproject.org/release-tools/tree/testresults.py to combined the manual test result into yocto-testresults. This will create new commit and tag for yocto-testresults. In certain condition this script might break, this can mean something wrong with any artefacts or yocto-testresults* repo. This will also create testreport.txt
			* Create release notes, finalize, get approval, and gpg sign.
			* create release notes in .rst and send to docs@lists.yoctoproject.org. (for 4.0 onwards)
			* Check the new documentation for the release is available on docs.yoctoproject.org (for 4.0 onward)
	* Sync the release out to the mirrors.		* Sync the release out to the mirrors.
	* Once sync out is complete, verify that pages work, and download and documentation links work.		* Once sync out is complete, verify that pages work, and download and documentation links work.
	* Tag the repos.		* Tag the repos.
	* Verify the items on the RELEASE CHECKLIST: https://wiki.yoctoproject.org/wiki/Yocto_Project_Release_Checklist		* Verify the items on the RELEASE CHECKLIST: https://wiki.yoctoproject.org/wiki/Yocto_Project_Release_Checklist
	* Post release announcement on Blog		* Post release announcement on Blog ( Deprecated ? )
	* Post release announcement on mailing lists (yocto and yocto-announce)		* Post release announcement on mailing lists (yocto and yocto-announce)
	* Update DISTRO and DISTRO_VERSION in master to be the main release+snapshot		* Update DISTRO and DISTRO_VERSION in master to be the main release+snapshot

Lee chee yang: /* Release of Build */

2023-12-11T05:48:35Z

Release of Build

Lee chee yang: /* Release Preparation Notes (from RP) */

2023-12-08T09:18:55Z

Release Preparation Notes (from RP)

← Older revision		Revision as of 09:18, 8 December 2023
Line 161:		Line 161:
	* *.md5sums - md5sum files of all files within the release		* *.md5sums - md5sum files of all files within the release

	== Release Preparation Notes ~~(from RP)~~ ==		== Release Preparation Notes ==

	Need to ensure we:		Need to ensure we:
	* Update LAYERSERIES_CORENAMES in meta/conf/layer.conf of OE-Core		* Update LAYERSERIES_CORENAMES in meta/conf/layer.conf of OE-Core
	* Update LAYERSERIES_COMPAT in meta/conf/layer.conf, meta-skeleton/conf/layer.conf, meta-selftest/conf/layer.conf of OE-Core		* Update LAYERSERIES_COMPAT in meta/conf/layer.conf, meta-skeleton/conf/layer.conf, meta-selftest/conf/layer.conf of OE-Core
	* Update LAYERSERIES_COMPAT in conf/layer.conf of meta-gplv2		* Update LAYERSERIES_COMPAT in conf/layer.conf of meta-gplv2 (not required for yocto-4.1 onward)
	* Update LAYERSERIES_COMPAT in conf/layer.conf of meta-mingw		* Update LAYERSERIES_COMPAT in conf/layer.conf of meta-mingw
	* Add release to scheulers.py in yocto-autobuilder		* Add release to scheulers.py in yocto-autobuilder
Line 173:		Line 173:
	* Copy perf-centos7.yoctoproject.org/master/qemux86 of yocto-buildstats to perf-centos7.yoctoproject.org/<branchname>/qemux86		* Copy perf-centos7.yoctoproject.org/master/qemux86 of yocto-buildstats to perf-centos7.yoctoproject.org/<branchname>/qemux86
	* Copy perf-ubuntu1604/master/qemux86 of yocto-buildstats to perf-ubuntu1604/<branchname>/qemux86		* Copy perf-ubuntu1604/master/qemux86 of yocto-buildstats to perf-ubuntu1604/<branchname>/qemux86
	* Update Poky version		* Update Poky version (not required for yocto-3.3 onward)
	* Update bitbake version		* Update bitbake version
	* Update build-appliance SRCREV		* Update build-appliance SRCREV

Lee chee yang: /* SDK Components */

2023-12-08T09:03:54Z

SDK Components

← Older revision		Revision as of 09:03, 8 December 2023
Line 153:		Line 153:
	* meta-toolchain tarballs for the following host/target combinations: i586/[arm\|i586\|mips\|ppc\|x86_64], x86_64/[arm\|i586\|mips\|ppc\|x86_64], arm64		* meta-toolchain tarballs for the following host/target combinations: i586/[arm\|i586\|mips\|ppc\|x86_64], x86_64/[arm\|i586\|mips\|ppc\|x86_64], arm64
	* Bootable SDK images for the following architectures: qemux86, qemux86-64, qemuarm, qemuarm64, qemumips, qemuppc		* Bootable SDK images for the following architectures: qemux86, qemux86-64, qemuarm, qemuarm64, qemumips, qemuppc
	* SDK plugins for the following IDEs: Anjuta, Eclipse

	Currently the SDK plugins are not being generated with the remaining build output. Jessica and Scott will need to define a process for this that makes sense before public release. There are issues to be take into consideration such as how the plugins are distributed (Anjuta and Eclipse have their own plugin repositories, for example).

	==== Other components ====		==== Other components ====

Lee chee yang: /* Distro Components */

2023-12-08T08:36:23Z

Distro Components

← Older revision		Revision as of 08:36, 8 December 2023
Line 147:		Line 147:
	* Bootable QEMU images of minimal and sato for the following architectures: qemux86, qemux86-64, qemuarm, qemuarm64, qemumips, qemuppc		* Bootable QEMU images of minimal and sato for the following architectures: qemux86, qemux86-64, qemuarm, qemuarm64, qemumips, qemuppc
	** A bootable QEMU image consists of a kernel file, a kernel modules tarball, and root filesystem tarball		** A bootable QEMU image consists of a kernel file, a kernel modules tarball, and root filesystem tarball
	* Non-emulated machine targets (e.g~~, edgerouter~~, beaglebone-yocto, genericx86, generic86-64) will include appropriate images (e.g, live images) of minimal and sato.		* Non-emulated machine targets (e.g, beaglebone-yocto, genericx86, generic86-64, generic-arm64) will include appropriate images (e.g, live images) of minimal and sato.

	==== SDK Components ====		==== SDK Components ====

MichaelHalstead at 19:58, 29 October 2020

2020-10-29T19:58:47Z

← Older revision		Revision as of 19:58, 29 October 2020
Line 226:		Line 226:
	* Create release notes, finalize, get approval, and gpg sign.		* Create release notes, finalize, get approval, and gpg sign.
	* Create the release and BSP pages on yoctoproject.org		* Create the release and BSP pages on yoctoproject.org
	* ~~Create~~ the documentation ~~links~~ for the release on yoctoproject.org		* Check the new documentation for the release is available on docs.yoctoproject.org
	* Sync the release out to the mirrors.		* Sync the release out to the mirrors.
	* Once sync out is complete, verify that pages work, and download and documentation links work.		* Once sync out is complete, verify that pages work, and download and documentation links work.

Armin Kuster: /* Last milestone */

2020-02-22T18:05:08Z

Last milestone

← Older revision		Revision as of 18:05, 22 February 2020
Line 201:		Line 201:

	===== Last milestone =====		===== Last milestone =====
	During the last milestone we generally will build from master and then branch when things are at the point where they're mostly stable. We do this to reduce the amount of work required to maintain two branches. Once we're seeing good daily builds and feel confident enough to branch, we will branch the poky, meta-~~qt3 and eclipse~~ repos to a branch named after the name of the release (dora, dylan, laverne, etc).		During the last milestone we generally will build from master and then branch when things are at the point where they're mostly stable. We do this to reduce the amount of work required to maintain two branches. Once we're seeing good daily builds and feel confident enough to branch, we will branch the poky, yocto-docs, meta-yocto, yocto-autobuilder-helper repos to a branch named after the name of the release (dora, dylan, laverne, zeus, etc).

	===== Prior to release build =====		===== Prior to release build =====

Armin Kuster: /* SDK Components */

2020-02-22T18:02:32Z

SDK Components

← Older revision		Revision as of 18:02, 22 February 2020
Line 151:		Line 151:
	==== SDK Components ====		==== SDK Components ====

	* meta-toolchain tarballs for the following host/target combinations: i586/[arm\|i586\|mips\|ppc\|x86_64], x86_64/[arm\|i586\|mips\|ppc\|x86_64]		* meta-toolchain tarballs for the following host/target combinations: i586/[arm\|i586\|mips\|ppc\|x86_64], x86_64/[arm\|i586\|mips\|ppc\|x86_64], arm64
	* Bootable SDK images for the following architectures: qemux86, qemux86-64, qemuarm, qemumips, qemuppc		* Bootable SDK images for the following architectures: qemux86, qemux86-64, qemuarm, qemuarm64, qemumips, qemuppc
	* SDK plugins for the following IDEs: Anjuta, Eclipse		* SDK plugins for the following IDEs: Anjuta, Eclipse

	Currently the SDK plugins are not being generated with the remaining build output. Jessica and Scott will need to define a process for this that makes sense before public release. There are issues to be take into consideration such as how the plugins are distributed (Anjuta and Eclipse have their own plugin repositories, for example).		Currently the SDK plugins are not being generated with the remaining build output. Jessica and Scott will need to define a process for this that makes sense before public release. There are issues to be take into consideration such as how the plugins are distributed (Anjuta and Eclipse have their own plugin repositories, for example).

	==== Other components ====		==== Other components ====

← Older revision		Revision as of 05:48, 11 December 2023
Line 210:		Line 210:

	===== Release of Build =====		===== Release of Build =====
	* Run the release script to stage the release. http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/bin/release_scripts/release.py. This script will do the following...		* Run the release script to stage the release. http://git.yoctoproject.org/cgit/cgit.cgi/yocto-autobuilder/tree/bin/release_scripts/release.py. This is not required for Kirkstone onwards. This script will do the following...
	- Create the staging directory.		- Create the staging directory.
	- Remove the rpm/deb directories.		- Remove the rpm/deb directories.
	- Delete duplicate files and extraneous blobs, and convert symlinks.		- Delete duplicate files and extraneous blobs, and convert symlinks.
	- Rename tarballs to reflect current naming conventions. For example. poky-<githash>.tar.bz2 should be renamed to poky-<release_name>-<release_number>.tar.bz2		- Rename tarballs to reflect current naming conventions. For example. poky-<githash>.tar.bz2 should be renamed to poky-<release_name>-<release_number>.tar.bz2
	- Generate the BSP tarballs		- Generate the BSP tarballs
Line 219:		Line 219:
	- Copy the adt-dev repo to the live site (For release lines prior to 2.0.)		- Copy the adt-dev repo to the live site (For release lines prior to 2.0.)
	- Create the md5sum table for the release		- Create the md5sum table for the release
	* Copy the staging directory to the downloads directory		* Copy the staging directory to the downloads directory (not required for Kirkstone onwards)
	* ~~gpg sign~~ the ~~md5sum table~~		* Combined the manual test result into yocto-testresults.
	* Create release notes, finalize, get approval, and gpg sign.		* Create release notes, finalize, get approval, and gpg sign.
	* Create the release and BSP pages on yoctoproject.org
	* Check the new documentation for the release is available on docs.yoctoproject.org		* Check the new documentation for the release is available on docs.yoctoproject.org
	* Sync the release out to the mirrors.		* Sync the release out to the mirrors.