Summary

Decide how tests for proposed kernels will get done. Where results will be available and how we proceed in case of problems.

Release Note

N/A

Rationale

In order for upstream stable changes being better checked for possible regressions we need to have testing of proposed kernels on a bigger hardware base. If anything breaks there, we need to have some process defined to make the kernel-team aware of those issues and prevent the proposed kernel to go to updates.

Assumptions

Design

Test Procedure

Test Results

Implementation

This section should describe a plan of action (the "how") to implement the changes discussed. Could include subsections like:

Unresolved issues

This should highlight any issues that should be addressed in further specifications, and not problems with the specification itself; since any specification with problems cannot be approved.

BoF agenda and discussion

Use this section to take notes during the BoF; if you keep it in the approved spec, use it for summarising what was discussed and note any options that were rejected.


CategorySpec

KernelTeam/Specs/KernelNattyStableProposedTesting (last edited 2010-10-20 13:28:47 by stefan-bader-canonical)