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
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?
   - Tarballs have been updated with the correct naming conventions.
   - Have we removed rpm and deb directories?
  - BSP tarballs have been generated.
   - Have we cleaned up image directories and removed duplicate entries?
   - rpm and deb directories have been removed.
   - Have we moved eclipse archives to their proper spots?
   - Machines subdirectories have been cleaned up. (Symlinks removed, dupes deleted, etc.)
   - Have we published the ADT? (Deprecated with Yocto 2.0 release and later.)
   - Eclipse plugins/archives have been published to correct spots.
   - Have we produced an md5sum file for the entire build?
   - ADT has been published, if applicable. (Deprecated with Yocto 2.0 release and later.)
  - Have we begun the mirror sync 5 days prior to release?
   - md5sum file for the entire release has been generated.
   - Have we checked that the mirror sync is working?
   - Release Notes have been created, finalized, and approved.
  - Have we created release notes?
   - Release Notes have been signed.
   - Have release notes been signed?
   - Release has been published to the downloads directory.
   - Have the release notes been copied to the downloads directory?
   - Repos have been tagged.
   - Does it have a link to the QA tests?
   - Release and BSP pages have been created on yoctoproject.org website.
  - Have we tagged the needed repos?
   - The README for each BSP has been checked and updated if necessary.
   - Have we inserted the easter egg?
   - Documentation links have been created on yoctoproject.org website.
   - Have we packaged the bsps?
   - Download links have been tested.
   - Have we put them up on the yoctoproject.org website? (Release page and BSP pages.)
   - The mirror sync has been triggered and completed successfully.
   - Have we tested their downloads?
   - The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
   - Have we verified the README for each release on the website?
   - Have we sent out the release email?

Revision as of 23:24, 20 October 2016

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: 

 - Tarballs have been updated with the correct naming conventions. 
 - BSP tarballs have been generated. 
 - rpm and deb directories have been removed. 
 - Machines subdirectories have been cleaned up. (Symlinks removed, dupes deleted, etc.)
 - Eclipse plugins/archives have been published to correct spots. 
 - ADT has been published, if applicable. (Deprecated with Yocto 2.0 release and later.)
 - md5sum file for the entire release has been generated. 
 - Release Notes have been created, finalized, and approved.
 - Release Notes have been signed.
 - Release has been published to the downloads directory.
 - Repos have been tagged.
 - Release and BSP pages have been created on yoctoproject.org website.
 - The README for each BSP has been checked and updated if necessary.
 - Documentation links have been created on yoctoproject.org website.
 - Download links have been tested.
 - The mirror sync has been triggered and completed successfully.
 - The release announcement has been sent to the appropriate mailing lists. (yocto and yocto-announce)
Retrieved from "https://wiki.yoctoproject.org/wiki/index.php?title=Yocto_Project_Release_Checklist&oldid=20867"