https://wiki.yoctoproject.org/wiki/api.php?action=feedcontributions&feedformat=atom&user=Agodard 2026-06-04T08:21:58Z User contributions MediaWiki 1.39.5 https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_Release_Checklist&diff=86815 2026-04-24T09:49:57Z

<p>Agodard: Add links to changes</p> <hr /> <div>Major Release <br /> <br /> * Week prior to build of release candidate<br /> ** Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle<br /> *** wic <br /> *** meta-yocto-bsp <br /> *** meta-yocto<br /> *** linux-firmware <br /> *** bootloaders (grub, syslinux, u-boot, gummiboot, etc..) <br /> *** hwdata <br /> *** pciutils <br /> *** util-linux <br /> *** i2c-tools <br /> *** alsa <br /> *** graphics drivers <br /> *** cryptodev <br /> *** systemtap<br /> *** perf<br /> *** linux-yocto<br /> <br /> * Prior to build of the first release candidate<br /> ** Is DISTRO_VERSION updated in poky.conf? (e.g. https://git.yoctoproject.org/meta-yocto/commit/?h=wrynose&amp;id=904846ae078ee20de073040ebb77c86e19250f56)<br /> ** Is SANITY_TESTED_DISTROS updated in poky.conf? (e.g. see above)<br /> ** Is bitbake version updated? (e.g. https://git.openembedded.org/bitbake/commit/?h=2.18&amp;id=33581c84f3a85008239acbd940501a35de48dc91)<br /> ** Are yocto-docs merged to the release branch?<br /> ** Has bitbake -f -c distrodata universe been run?<br /> ** 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/)<br /> ** 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/)<br /> ** Update Toaster fixtures files<br /> ** Update SRCREVs in build-appliance-image (e.g. https://git.openembedded.org/openembedded-core/commit/?h=wrynose&amp;id=42fa856a00ac16b2a7a83d7ecfa60a5be192b16c)<br /> <br /> * After the final release candidate has returned from QA and is approved, verify the following:<br /> ** BSP tarballs have been generated.<br /> ** Release Notes have been created, finalized, and approved.<br /> ** Release Notes have been signed.<br /> ** Repos have been tagged with correct commit and signature. <br /> ** The README for each BSP has been checked and updated if necessary.<br /> ** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.<br /> ** The kernel.org mirror sync has been triggered and completed successfully.<br /> ** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)<br /> ** docs.yoctoproject.org updated correct dropdown version.<br /> ** Files to update in yocto-docs:<br /> *** 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/)<br /> *** Update documentation/ref-manual/svg/releases.svg (e.g. https://lore.kernel.org/yocto-docs/20251204-release-updates-v2-2-04ca6c26ddd5@bootlin.com/)<br /> ** Files to update in yocto-autobuilder2:<br /> *** 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/)<br /> ** Files to update in yocto-autobuilder-helper:<br /> *** Update scripts/release-parser.py<br /> ** Files to update in yocto-metrics:<br /> *** Update patch-status/releases.csv</div>

Agodard https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_Release_Checklist&diff=86811 2026-04-24T07:46:27Z

<p>Agodard: Update the page to remove deprecated content and add other locations in the code to update</p> <hr /> <div>Major Release <br /> <br /> * Week prior to build of release candidate<br /> ** Updates to the following packages will have occurred. DO NO PANIC, these come late in the release cycle<br /> *** wic <br /> *** meta-yocto-bsp <br /> *** meta-yocto<br /> *** linux-firmware <br /> *** bootloaders (grub, syslinux, u-boot, gummiboot, etc..) <br /> *** hwdata <br /> *** pciutils <br /> *** util-linux <br /> *** i2c-tools <br /> *** alsa <br /> *** graphics drivers <br /> *** cryptodev <br /> *** systemtap<br /> *** perf<br /> *** linux-yocto<br /> <br /> * Prior to build of the first release candidate<br /> ** Is DISTRO_VERSION updated in poky.conf?<br /> ** Is SDK_VERSION updated in poky.conf?<br /> ** Is SANITY_TESTED_DISTROS updated in poky.conf?<br /> ** Are yocto-docs merged to the release branch?<br /> ** Has bitbake -f -c distrodata universe been run?<br /> ** Add a new bitbake-setup configuration file in BitBake's registry (create a new one, do not delete old ones)<br /> <br /> * After the final release candidate has returned from QA and is approved, verify the following:<br /> ** BSP tarballs have been generated.<br /> ** Release Notes have been created, finalized, and approved.<br /> ** Release Notes have been signed.<br /> ** Repos have been tagged with correct commit and signature. <br /> ** The README for each BSP has been checked and updated if necessary.<br /> ** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.<br /> ** The kernel.org mirror sync has been triggered and completed successfully.<br /> ** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)<br /> ** docs.yoctoproject.org updated correct dropdown version.<br /> ** Files to update in yocto-docs:<br /> *** Create new release note templates in documentation/migration-guides/<br /> *** Update documentation/ref-manual/svg/releases.svg<br /> ** Files to update in yocto-autobuilder2:<br /> *** update workers_prev_releases in config.py<br /> ** Files to update in yocto-autobuilder-helper:<br /> *** Update scripts/release-parser.py<br /> ** Files to update in yocto-metrics:<br /> *** Update patch-status/releases.csv</div>

Agodard