Processes and Activities

Yocto Release Process

Steps to release Yocto:

Run an autobuilder "generate-release" build. This will create images in /srv/www/vhosts/autobuilder.pokylinux.org/generate-release/<datestamp>/. Rename these files with the appropriate release name and version (Scott will have a script to do this by the next release).

For post-Green releases, there will be a release staging area that will be used to mirror the output before the files are released on the public web site.

On release branch:

• Set DISTRO_VERSION in poky.conf
• Update handbook references to stable release (introduction.xml, master branch needs this too)
• Update version reference and updated date in handbook (poky-handbook.xml)
• git commit -a -m "Purple 3.2 Release"
• git tag -a purple-3.2 -m "Tag Purple 3.2"
• git archive purple-3.2 --prefix=purple-3.2/ | bzip2 > /tmp/poky-purple-3.2.tar.bz2 scp /tmp/poky-purple-3.2.tar.bz2 o- hand.com:/srv/www/pokylinux.org/releases/poky-purple-3.2.tar.bz2

On master branch:

• Set DISTRO_VERSION in poky.conf to new version
• Update version reference and updated date in handbook (poky-handbook.xml)

• cd handbook
• make
• scp -r poky-handbook.tgz poky-handbook.html poky-handbook.pdf *.png *.xml *.css *.svg o-hand.com:/srv/www/pokylinux.org/releases/purple-3.2/doc/
• scp -r poky-handbook.tgz poky-handbook.html *.png *.xml *.css *.svg o-hand.com:/srv/www/pokylinux.org/releases/doc/

(or copy across by hand when remotely connected to machine?)

• Edit web pages (website is controlled from a git repo)
  • support/index.php
  • getit/index.php
  • index.php
  • poky-wp-theme/common-funcs.inc
  • poky-wp-theme/front-page.php
• Post release announcement on Blog
• Post release announcement on mailing list

Scott's Poky Green Notes

To avoid a mad scramble during the final hours before a release, things need to be spaced out more - there should be a 24-hour period where the images to be released are frozen, tested, and mirrored to the public web server. This would be a good time to write up the release announcement/blog posts, etc.

generate-release did not copy over the sato and sdk images because they were ext3 filesystems and the script was looking for files with a .ext2 extension.

There needs to be a sign-off process for the images, to ensure they have at least been booted and to check for silly errors (e.g, Richard pointed out the first time that I had used 3.2 in the image filenames when Green was 3.3)