Yocto Project Release Checklist: Difference between revisions

From Yocto Project
Jump to navigationJump to search
m (Added a couple of things to check. Added comment about ADT publishing being deprecated for anything after YP 2.0 release. Comment about creating pages for BSPs as well as the release itself.)
(Add links to changes)
 
(15 intermediate revisions by 6 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
* After the final release candidate has returned from QA and is approved, verify the following:
  - Have we checked and updated all tarballs if needed using consistent naming conventions?
** BSP tarballs have been generated.
  - Have we removed rpm and deb directories?
** Release Notes have been created, finalized, and approved.
  - Have we cleaned up image directories and removed duplicate entries?
** Release Notes have been signed.
  - Have we moved eclipse archives to their proper spots?
** Repos have been tagged with correct commit and signature.
  - Have we published the ADT? (Deprecated with Yocto 2.0 release and later.)
** The README for each BSP has been checked and updated if necessary.
  - Have we produced an md5sum file for the entire build?
** Artifacts correctly moved to https://downloads.yoctoproject.org/releases/yocto/.
  - Have we begun the mirror sync 5 days prior to release?
** The kernel.org mirror sync has been triggered and completed successfully.
  - Have we checked that the mirror sync is working?
** The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
  - Have we created release notes?
** docs.yoctoproject.org updated correct dropdown version.
  - Have release notes been signed?
** Files to update in yocto-docs:
  - Have the release notes been copied to the downloads directory?
*** 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/)
  - Does it have a link to the QA tests?
*** Update documentation/ref-manual/svg/releases.svg (e.g. https://lore.kernel.org/yocto-docs/20251204-release-updates-v2-2-04ca6c26ddd5@bootlin.com/)
  - Have we tagged the needed repos?
** Files to update in yocto-autobuilder2:
  - Have we inserted the easter egg?
*** 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/)
  - Have we packaged the bsps?
** Files to update in yocto-autobuilder-helper:
  - Have we put them up on the yoctoproject.org website? (Release page and BSP pages.)
*** Update scripts/release-parser.py
  - Have we tested their downloads?
** Files to update in yocto-metrics:
  - Have we verified the README for each release on the website?
*** Update patch-status/releases.csv
  - Have we sent out the release email?

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"