Yocto Project Release Checklist: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
No edit summary
Line 22: Line 22:
** Is DISTRO_VERSION updated in poky.conf? (e.g. https://git.yoctoproject.org/meta-yocto/commit/?h=wrynose&id=904846ae078ee20de073040ebb77c86e19250f56)
** Is DISTRO_VERSION updated in poky.conf? (e.g. https://git.yoctoproject.org/meta-yocto/commit/?h=wrynose&id=904846ae078ee20de073040ebb77c86e19250f56)
** Is SANITY_TESTED_DISTROS updated in poky.conf? (e.g. see above)
** Is SANITY_TESTED_DISTROS updated in poky.conf? (e.g. see above)
** 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?
Line 27: Line 28:
** 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/)
** 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 Toaster fixtures files
** Update SRCREVs in build-appliance-image
** 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:

Revision as of 09:17, 24 April 2026

Major Release

  • 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
      • wic
      • meta-yocto-bsp
      • meta-yocto
      • linux-firmware
      • bootloaders (grub, syslinux, u-boot, gummiboot, etc..)
      • hwdata
      • pciutils
      • util-linux
      • i2c-tools
      • alsa
      • graphics drivers
      • cryptodev
      • systemtap
      • perf
      • linux-yocto
  • After the final release candidate has returned from QA and is approved, verify the following:
    • BSP tarballs have been generated.
    • Release Notes have been created, finalized, and approved.
    • Release Notes have been signed.
    • Repos have been tagged with correct commit and signature.
    • The README for each BSP has been checked and updated if necessary.
    • Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.
    • 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)
    • 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