LandscapeUpdates

Differences between revisions 18 and 21 (spanning 3 versions)
Revision 18 as of 2009-01-06 20:35:29
Size: 2471
Editor: 189-75-128-19
Comment:
Revision 21 as of 2009-01-12 16:43:38
Size: 2820
Editor: 189-31-214-42
Comment:
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
'''DRAFT, DO NOT COMMENT ABOUT THIS YET - Andreas - Jan/2008''' '''DRAFT, please send comments to andreas at ubuntu.com'''
Line 3: Line 3:
This document describes the policy for updating Landscape client packages in a stable supported distro, including LTS. This document describes the policy for updating Landscape client packages in a stable supported distro, including LTS. It is also the aim of this document to provide an example of the needed minimum requirements for any upstream project that wants to push updates to an Ubuntu stable release.
Line 14: Line 14:
 * the code must be developed according to the TDD (Test Driven Development) model. For reference, see http://en.wikipedia.org/wiki/Test-driven_development. Basically, it means that every code change must be covered by a test. Yes, really.
Line 23: Line 24:
 * upgrade test from previous distribution to the current one. If the current distribution is an LTS one, the upgrade path from the previous LTS distro must also be exercised. This upgrade test must be performed using do-release-upgrade  * upgrade test from previous distribution to the current one. If the current distribution is an LTS one, the upgrade path from the previous LTS distro must also be exercised.

DRAFT, please send comments to andreas at ubuntu.com

This document describes the policy for updating Landscape client packages in a stable supported distro, including LTS. It is also the aim of this document to provide an example of the needed minimum requirements for any upstream project that wants to push updates to an Ubuntu stable release.

Landscape is a commercial service from Canonical which periodically offers new features to its customers. Being a client-server product, the client part needs to be periodically updated in order to take advantage of the new features. Therefore, in addition to bug fixes, new features are allowed in an update as long as the conditions outlined below are met.

QA Process

This is the mandatory QA process that the proposed packages have to pass. The following requirements must be met:

The above tests exercise the code changes and must be performed by a member of the Landscape team. The packaging changes need an extra QA procedure outlined below.

Packaging QA

The objective of the separate packaging QA is to test:

  • package upgrades
  • package installation from scratch
  • distribution upgrade

The resulting package, with all the changes in place, must undergo and pass the following additional QA procedures:

  • upgrade test from previous distribution to the current one. If the current distribution is an LTS one, the upgrade path from the previous LTS distro must also be exercised.
  • upgrade test from previous version of the package. This test must be performed with:
    • apt-get install/upgrade
    • using the Landscape service itself
  • installation from scratch in the current distribution:
    • using apt-get

The above tests can be performed by any QA engineer.

Requesting the SRU

The SRU should be requested as usual (StableReleaseUpdates) with the additional note about having the above steps being completed.

LandscapeUpdates (last edited 2025-06-25 18:55:27 by ahasenack)