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.)
No edit summary
 
(10 intermediate revisions by 4 users not shown)
Line 27: Line 27:
   -  Has an updated distro_alias.inc patch been accepted?
   -  Has an updated distro_alias.inc patch been accepted?


- 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?
   - Have the release notes been copied to the downloads directory?
  - Does it have a link to the QA tests?
   - Have we tagged the needed repos?
  - Have we inserted the easter egg?
  - Have we packaged the bsps?
  - Have we put them up on the yoctoproject.org website? (Release page and BSP pages.)
  - Have we tested their downloads?
  - Have we verified the README for each release on the website?
  - Have we sent out the release email?

Latest revision as of 08:59, 6 October 2025

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?
 -  Has an updated distro_alias.inc patch been accepted?

- 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.