Checklist/XenHypervisorRelease

This page is a checklist for Xen developers doing a release.

Disabling debug

Sometime after the initial RCs, and before the final RC, disable debug by default:

In Config.mk, change

debug ?= y

to

debug ?= n

Checklist for branching a release

Here ${V} will be the version to be released, and ${V+1} stands for the next release. For example, ${V} might be 4.3, and ${V+1} would be 4.4.

Create new branch for git and mercurial

• Create staging-${V} and stable-${V} branches in the main git repo

[Detailed instructions here]

Update version numbers in the development branch

• Change the version number in xen/Makefile by setting XEN_VERSION and XEN_SUBVERSION appropriately.

• Update the ASCII art version in README

Update version numbers in the release branch

• Change the version number in xen/Makefile by setting XEN_VERSION and XEN_SUBVERSION appropriately.

• Remove '-rc' from the ASCII art in README

• Update url for qemu trees

In Config.mk, modify both instances of QEMU_UPSTREAM_URL and both instances of QEMU_REMOTE, replacing -unstable with -${V}

Checklist for the final release

Everything on this list must be done in advance of any public press release, preferably one week ahead of time, to allow for the announcement to be postponed if necessary.

• Create release tags for qemu

Create the tag qemu-xen-${V} for qemu-xen, and xen-${V} for qemu-traditional

• Update the qemu tags from a hash to a tag

In Config.mk, modify QEMU_UPSTREAM_REVISION and QEMU_TAG to the release tag for qemus (see above for exact names).