Uninative Release Process

Uninative Release Engineering Process

This document describes release engineering procedures for releasing new versions of Uninative.

Requests for a new uninative release will generally come from Richard Purdie.

Build the tools

Build the buildtools using default revision of master branch, unless given other specific criteria. The buildtools may also come from a full run of a nightly, but typically an explicit run of buildtools build happens.

Create the Release Directory

On the build worker where the buildtools build occurred, create the new release directory in <path-to-download-location>/uninative/<release_#>

Using 1.7 as an example...

On the "old" yoctoproject.org AB cluster, this would be: /srv/www/vhosts/downloads.yoctoproject.org/releases/uninative/1.7

On the "new" yocto.io AB cluster, this would be: /srv/autobuilder/downloads.yoctoproject.org/releases/uninative/1.7

You should use http://downloads.yoctoproject.org/releases/uninative/ as a reference to determine what the next version number should be.

Releases are versioned sequentially in the format of M.m. i.e. 1.5, 1.6, 1.7, etc. This release naming does NOT correspond to specific Yocto releases. Uninative releases may come from any build or Yocto release, so they do not align with any specific given Major/Minor/Point release.

Copy the Files

Still on the build worker where the build happens, the requisite files will be found in:

/home/pokybuild/yocto-autobuilder/yocto-worker/buildtools/build/build/tmp/deploy/sdk

Copy the following files to the release directory:

• i686-nativesdk-libc.host.manifest
• i686-nativesdk-libc.target.manifest
• i686-nativesdk-libc.tar.bz2
• x86_64-nativesdk-libc.host.manifest
• x86_64-nativesdk-libc.target.manifest
• x86_64-nativesdk-libc.tar.bz2

Publishing

In most cases the sync out to the external mirrors will happen automatically. In the event that it does not, manually start the sync out. If assistance is needed with this, contact Michael Halstead.

Tagging

Uninative releases are tagged in the following format:

uninative-<version>. i.e. uninative-1.5, uninative-1.6, uninative-1.7, etc.

Currently, Michael Halstead should be contacted for signing and pushing tags.

Tags are pushed for both poky and oe-core.

Announcements

We currently do not formally announce uninative releases. Simply notify Richard Purdie and any other relevant people that the release is published.