Yocto Project Release Checklist: Difference between revisions

From Yocto Project
Jump to navigationJump to search
No edit summary
(Add links to changes)
 
(13 intermediate revisions by 5 users not shown)
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? (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?
  - 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, 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:
  - Tarballs have been updated with the correct naming conventions. 
** BSP tarballs have been generated.
  - BSP tarballs have been generated.  
** Release Notes have been created, finalized, and approved.
  - rpm and deb directories have been removed.
** Release Notes have been signed.
  - Machines subdirectories have been cleaned up. (Symlinks removed, dupes deleted, etc.)
** Repos have been tagged with correct commit and signature.  
  - Eclipse plugins/archives have been published to correct spots.
** The README for each BSP has been checked and updated if necessary.
  - ADT has been published, if applicable. (Deprecated with Yocto 2.0 release and later.)
** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.
  - md5sum file for the entire release has been generated.
** The kernel.org mirror sync has been triggered and completed successfully.
  - Release Notes have been created, finalized, and approved.
** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
  - Release Notes have been signed.
** docs.yoctoproject.org updated correct dropdown version.
  - Repos have been tagged.
** Files to update in yocto-docs:
  - Release and BSP pages have been created on yoctoproject.org website.
*** 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/)
  - The README for each BSP has been checked and updated if necessary.
*** Update documentation/ref-manual/svg/releases.svg (e.g. https://lore.kernel.org/yocto-docs/20251204-release-updates-v2-2-04ca6c26ddd5@bootlin.com/)
  - Documentation links have been created on yoctoproject.org website.
** Files to update in yocto-autobuilder2:
  - Download links have been tested.
*** 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/)
  - The mirror sync has been triggered and completed successfully.
** Files to update in yocto-autobuilder-helper:
  - The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
*** Update scripts/release-parser.py
** Files to update in yocto-metrics:
*** Update patch-status/releases.csv

Latest revision as of 09:49, 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
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_Release_Checklist&oldid=86815"