ServerImageValidationAndQA

Revision 2 as of 2011-05-18 17:50:14

Clear message

Summary

Release Note

For the 11.10 cycle, Ubuntu will support ARM server images for all available platforms.

Rationale

As per server-o-arm-image, we'll be implementing server images on ARM for the 11.10 cycle. As ARM has never been target of a server image before, extensive QA and validation efforts

User stories

  • Alpha wishes to build a cluster of ARM servers, and wants software that is known to work for all her usecase
  • Beta is migrating from Ubuntu i386 -> armel on new hardware, and wants the same level of functionality they have come to expect on i386

  • Delta is a system manufacturer creating ARM servers, and wishes to ship a well-tested product with their hardware

Assumptions

  • There is no fundament area where ARM servers are unable to provide similar functionality to x86 (i.e. virtualization)

Design

You can have subsections that better describe specific parts of the issue.

Implementation

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

UI Changes

Should cover changes required to the UI, or specific UI that is required to implement this

Code Changes

Code changes should include an overview of what needs to change, and in some cases even the specific details.

Migration

Include:

  • data migration, if any
  • redirects from old URLs to new ones, if any
  • how users will be pointed to the new way of doing things, if necessary.

Test/Demo Plan

It's important that we are able to test new features, and demonstrate them to users. Use this section to describe a short plan that anybody can follow that demonstrates the feature is working. This can then be used during testing, and to show off after release. Please add an entry to http://testcases.qa.ubuntu.com/Coverage/NewFeatures for tracking test coverage.

This need not be added or completed until the specification is nearing beta.

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