Uninative Release Process

Uninative Release Engineering Process

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

DRAFT

• Where to obtain the files

The Uninative files are found in the toolchain directory of a given build. i.e. http://downloads.yoctoproject.org/releases/yocto/yocto-2.0/toolchain/ Richard Purdie will generally be the source for directing when a new release needs to happen and what branch/revisions to use for the build, or identifying a specific existing release or release candidate.

• What to publish

• 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

• Where to publish

Uninative releases are published at http://downloads.yoctoproject.org/releases/uninative/

• Release Naming

Releases are versioned sequentially in the format of M.m. i.e. 1.0, 1.1, 1.2. This release naming does NOT correspond to specific Yocto releases. Uninative releases may come from any build or Yocto release, as needed and are simply numbered incrementally.

• Tagging

Uninative releases should be tagged using a tag in the following format:

uninative-<version>. i.e. uninative-1.0, uninative-1.1, uninative-1.2

??? Signed tags? oe-core and poky both? (Probably. Need to confirm repo and signing)

??? Who pushes tags.

• Announcements

??? Do we need to, should we, announce to a mailing list?

??? Do we need to announce