Yocto Project Release Checklist: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(Update the page to remove deprecated content and add other locations in the code to update)
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

Revision as of 07:46, 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
  • Prior to build of the first release candidate
    • Is DISTRO_VERSION updated in poky.conf?
    • Is SDK_VERSION updated in poky.conf?
    • Is SANITY_TESTED_DISTROS updated in poky.conf?
    • Are yocto-docs merged to the release branch?
    • 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)
  • 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
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_Release_Checklist&oldid=86811"