Ubuntu

Automated Tests for Proposed Kernels

Registered by Stefan Bader on 2010-10-05

Discuss how proposed kernels will get tested and how we handle results (regressions mostly).

Read the full specification

Blueprint information

Status:: Complete

Approver:: Pete Graner

Priority:: Essential

Drafter:: Stefan Bader

Direction:: Approved

Assignee:: Stefan Bader

Definition:: Superseded

Series goal:: None

Implementation:: Unknown

Milestone target:: None

Completed by: Andy Whitcroft on 2010-11-04

Related branches

Related bugs

Sprints

uds-n

Whiteboard

The goal of this discussion is to
[canonical-kernel-team] Define the tests that will be done when new proposed kernels are uploaded: TODO
[canonical-kernel-team] Define the reporting of failures and the resulting actions: TODO
[canonical-kernel-team] Have a written document that describes the testing and possible interfaces to add/change things: TODO
[canonical-kernel-team] Write down what steps are required/optional and convert them into work-items: TODO